[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141202164024.GA10918@htj.dyndns.org>
Date: Tue, 2 Dec 2014 11:40:24 -0500
From: Tejun Heo <htejun@...il.com>
To: Christoph Lameter <cl@...ux.com>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Final per cpu consistency patch for -next or late in 3.19 merge
period
Hello, Christoph.
On Fri, Nov 28, 2014 at 12:31:22PM -0600, Christoph Lameter wrote:
> This is the final patch to remove __get_cpu_var. I checked -next and there
> are no remaining uses of __get_cpu_var. So either merge this to -next or
> wait until 3.19 late.
>
> However, if we wait till 3.19 then I may have to do another pass if
> people add more uses of __get_cpu_var and submit another patch.
>
> From: Christoph Lameter <cl@...ux.com>
> Date: Tue, 29 Jul 2014 16:09:54 -0500
> Subject: [PATCH] Remove __get_cpu_var and __raw_get_cpu_var macros
>
> No user is left in the kernel source tree. Therefore we can
> drop the definitions.
>
> This is the final merge of the transition away from __get_cpu_var.
> After this patch the kernel will not build if anyone uses __get_cpu_var.
Can you please update Documentation/local_ops.txt and comments which
contain __get_cpu_var() and send the updated patch to Andrew?
Andrew, this is removal of the two deprecated per-cpu accessors. All
the existing users are gone from the devel branches and thus from -mm.
Can you please route this once Christoph posts an updated version?
Thanks.
--
tejun
--
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