[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1326333904.5695.311.camel@debian>
Date: Thu, 12 Jan 2012 10:05:04 +0800
From: "Alex,Shi" <alex.shi@...el.com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: "tj@...nel.org" <tj@...nel.org>, Christoph Lameter <cl@...two.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"eric.dumazet@...il.com" <eric.dumazet@...il.com>,
"Huang, Ying" <ying.huang@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"avi@...hat.com" <avi@...hat.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
David Miller <davem@...emloft.net>,
"kaber@...sh.net" <kaber@...sh.net>,
"a.p.zijlstra@...llo.nl" <a.p.zijlstra@...llo.nl>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 3/3] Code clean up for percpu_xxx() functions
On Wed, 2012-01-11 at 16:44 -0800, H. Peter Anvin wrote:
> On 01/11/2012 09:19 AM, tj@...nel.org wrote:
> >
> > Alex, can you please collect all patches into a single patchset?
> > Please split it such that, usage changes are per-system so that they
> > can be routed through respective subsystems (x86 or net) and updates
> > to percpu proper which can be applied after other changes have been
> > applied. It would probably be best to route these patches separately
> > rather than all through percpu as it touches a lot of different places
> > and is likely to cause conflicts. I *think* the best way would be,
> >
> > * Submit per-subsystem patches and get them merged to subsystem trees.
> >
> > * (Optional) Apply a patch to mark unused interface deprecated in
> > percpu tree, so that new usages in linux-next can be detected.
> >
> > * Towards the end of the next merge window, merge a patch to actually
> > kill the old interface.
> >
>
> That sounds like a good idea.
I will try to do so. Many thanks for the advices!
>
> -hpa
--
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