linux-kernel - RE: [PATCH] atomic: add *_dec_not

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6D8AD0D@saturn3.aculab.com>
Date:	Wed, 4 May 2011 09:05:53 +0100
From:	"David Laight" <David.Laight@...LAB.COM>
To:	"Sven Eckelmann" <sven@...fation.org>,
	<linux-kernel@...r.kernel.org>
Cc:	<linux-arch@...r.kernel.org>, <linux-mips@...ux-mips.org>,
	<linux-m32r@...linux-m32r.org>, <linux-ia64@...r.kernel.org>,
	<linux-parisc@...r.kernel.org>, <linux-cris-kernel@...s.com>,
	<linux-s390@...r.kernel.org>, <linux-sh@...r.kernel.org>,
	<x86@...nel.org>, "Chris Metcalf" <cmetcalf@...era.com>,
	"David Howells" <dhowells@...hat.com>,
	<linux-m68k@...ts.linux-m68k.org>, <linux-am33-list@...hat.com>,
	<linux-alpha@...r.kernel.org>, <sparclinux@...r.kernel.org>,
	<uclinux-dist-devel@...ckfin.uclinux.org>,
	<linuxppc-dev@...ts.ozlabs.org>,
	<linux-arm-kernel@...ts.infradead.org>
Subject: RE: [PATCH] atomic: add *_dec_not_zero

 
> 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.

	David


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/