[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1704171113040.2327@nanos>
Date: Mon, 17 Apr 2017 11:14:23 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: "Jason A. Donenfeld" <Jason@...c4.com>
cc: LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Sebastian Siewior <bigeasy@...utronix.de>,
Steffen Klassert <steffen.klassert@...unet.com>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>
Subject: Re: [patch 03/20] padata: Make padata_alloc() static
On Sun, 16 Apr 2017, Jason A. Donenfeld wrote:
> I rather like this option of padata, which, since it lives in
> kernel/padata.c and linux/padata.h, should be generic and useful for
> other components. Seems like the ability to allocate it for a
> particular set of worker CPUs and callback CPUs could be useful down
> the line. Would rather not see it become static.
It's simple enough to export it once there is an actual user. Just keeping
stuff global because it might be useful somewhere down the road is really
pointless.
Thanks,
tglx
Powered by blists - more mailing lists