From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from e32.co.us.ibm.com ([32.97.110.150]:35799 "EHLO e32.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752536AbYDUOz1 (ORCPT ); Mon, 21 Apr 2008 10:55:27 -0400 Date: Mon, 21 Apr 2008 07:55:25 -0700 From: "Paul E. McKenney" To: Johannes Berg Cc: linux-kernel@vger.kernel.org, Josh Triplett , linux-wireless@vger.kernel.org, linux-sparse@vger.kernel.org Subject: Re: [RFC 0/3] Examples for the new sparse context tracking functionality Message-ID: <20080421145525.GB9153@linux.vnet.ibm.com> (sfid-20080421_165618_830060_38E22132) Reply-To: paulmck@linux.vnet.ibm.com References: <20080410134810.629048000@sipsolutions.net> <20080419233338.GG20138@linux.vnet.ibm.com> <1208766355.26186.37.camel@johannes.berg> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1208766355.26186.37.camel@johannes.berg> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, Apr 21, 2008 at 10:25:55AM +0200, Johannes Berg wrote: > > > At some point in the future, we might want to distinguish between > > the different flavors of RCU -- except that there is already common > > code that doesn't care which flavor of RCU is in use, as long as > > some sort of RCU is present. So make that "some point in the distant > > future"... > > No big deal, just declare > > my_specific_rcu_get() __acquires(RCU) __acquires(specificRCU); > > and then annotate whatever needs the specific RCU type with > __requires(specificRCU) Cute!!! I didn't realize you could mark a single interface with multiple __acquires() markings. So if there is at least one match, sparse is happy? Thanx, Paul