From: Sven Eckelmann <sven@narfation•org>
To: "David Laight" <David.Laight@aculab•com>
Cc: linux-arch@vger•kernel.org, linux-mips@linux-mips•org,
linux-m32r@ml•linux-m32r.org, linux-ia64@vger•kernel.org,
linux-cris-kernel@axis•com, linux-parisc@vger•kernel.org,
linux-s390@vger•kernel.org, linux-sh@vger•kernel.org,
linux-kernel@vger•kernel.org, Chris Metcalf <cmetcalf@tilera•com>,
David Howells <dhowells@redhat•com>,
linux-m68k@lists•linux-m68k.org, linux-am33-list@redhat•com,
linux-alpha@vger•kernel.org, sparclinux@vger•kernel.org,
uclinux-dist-devel@blackfin•uclinux.org, x86@kernel•org,
linuxppc-dev@lists•ozlabs.org,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH] atomic: add *_dec_not_zero
Date: Wed, 4 May 2011 10:21:16 +0200 [thread overview]
Message-ID: <201105041021.22082.sven@narfation.org> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6D8AD0D@saturn3.aculab.com>
[-- Attachment #1: Type: Text/Plain, Size: 640 bytes --]
On Wednesday 04 May 2011 10:05:53 David Laight wrote:
> > Introduce an *_dec_not_zero operation. Make this a special case of
> > *_add_unless because batman-adv uses atomic_dec_not_zero in different
> > places like re-broadcast queue or aggregation queue management. There
> > are other non-final patches which may also want to use this macro.
>
> Isn't there a place where a default definition of this can be
> defined? Instead of adding it separately to every architecture.
Not that I would know about such a place - and all other atomic* macro
definitions also suggest that there is no such place.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-05-04 8:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 21:30 [PATCH] atomic: add *_dec_not_zero Sven Eckelmann
2011-05-04 4:44 ` Mike Frysinger
2011-05-04 15:04 ` James Bottomley
2011-05-04 6:12 ` David Miller
2011-05-04 7:03 ` Ingo Molnar
2011-05-04 8:05 ` David Laight
2011-05-04 8:21 ` Sven Eckelmann [this message]
2011-05-04 8:33 ` Mike Frysinger
2011-05-04 10:48 ` Jesper Nilsson
2011-05-04 11:02 ` Ralf Baechle
2011-05-04 11:53 ` David Howells
2011-05-04 12:09 ` Chris Metcalf
2011-05-04 12:17 ` Geert Uytterhoeven
2011-05-04 17:27 ` Will Deacon
2011-05-04 18:13 ` Matt Turner
2011-05-08 9:24 ` Russell King - ARM Linux
2011-05-08 9:33 ` Sven Eckelmann
2011-05-09 2:38 ` Mike Frysinger
2011-05-08 22:15 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201105041021.22082.sven@narfation.org \
--to=sven@narfation$(echo .)org \
--cc=David.Laight@aculab$(echo .)com \
--cc=cmetcalf@tilera$(echo .)com \
--cc=dhowells@redhat$(echo .)com \
--cc=linux-alpha@vger$(echo .)kernel.org \
--cc=linux-am33-list@redhat$(echo .)com \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-cris-kernel@axis$(echo .)com \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-m32r@ml$(echo .)linux-m32r.org \
--cc=linux-m68k@lists$(echo .)linux-m68k.org \
--cc=linux-mips@linux-mips$(echo .)org \
--cc=linux-parisc@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linux-sh@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=sparclinux@vger$(echo .)kernel.org \
--cc=uclinux-dist-devel@blackfin$(echo .)uclinux.org \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox