[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160104222153.GH32217@linux.vnet.ibm.com>
Date: Mon, 4 Jan 2016 14:21:53 -0800
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Boqun Feng <boqun.feng@...il.com>
Cc: linux-sparse@...r.kernel.org, linux-kernel@...r.kernel.org,
Christopher Li <sparse@...isli.org>,
Josh Triplett <josh@...htriplett.org>,
Steven Rostedt <rostedt@...dmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Lai Jiangshan <jiangshanlai@...il.com>,
Andy Whitcroft <apw@...onical.com>,
Joe Perches <joe@...ches.com>,
Thomas Gleixner <tglx@...utronix.de>,
Jiang Liu <jiang.liu@...ux.intel.com>,
Marc Zyngier <marc.zyngier@....com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Russell King <rmk+kernel@....linux.org.uk>,
Brian Norris <computersforpeace@...il.com>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [RFC v2 0/3] sparse: Introduce __private to privatize members of
structs
On Tue, Dec 29, 2015 at 12:18:45PM +0800, Boqun Feng wrote:
> Hi all,
>
> This is v2 of __private.
>
> Link for v1: http://marc.info/?l=linux-sparse&m=144988906932520&w=2
>
> Change since v1:
>
> * #undef __irqd_to_state after used (Peter Zijlstra)
>
>
> This patchset introduces a __private modifier for sparse to detect misuses of
> private members of structs. This could make maintenace a little easier and
> prevent some potential bugs.
>
>
> This patchset consists of three patches:
>
> 1. Introduce __private and related macro, also improve compiler.h a litte
> bit
>
> 2. Privatize rcu_node::lock
>
> 3. Privatize irq_common_data::state_use_accessors
>
> This patchset is against
>
> -rcu/rcu/next c95a158356397844a5a6deb0bd58758084f891df
>
> because it depends on commits:
>
> "rcu: Create transitive rnp->lock acquisition functions"
> and
> "rcu: Add transitivity to remaining rcu_node ->lock acquisitions
>
>
> Tested by 0day.
>
> Looking forward to any suggestion, question and comment ;-)
Queued for review and testing, along with Thomas's Reviewed-by. If all
goes well, I expect to send them upstream in the 4.6 merge window.
Thanx, Paul
--
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/
Powered by blists - more mailing lists