From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: [patch 03/20] padata: Make padata_alloc() static Date: Mon, 17 Apr 2017 11:14:23 +0200 (CEST) Message-ID: References: <20170415170107.643253702@linutronix.de> <20170415171651.483363066@linutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: LKML , Peter Zijlstra , Ingo Molnar , Steven Rostedt , Sebastian Siewior , Steffen Klassert , Linux Crypto Mailing List To: "Jason A. Donenfeld" Return-path: Received: from Galois.linutronix.de ([146.0.238.70]:47144 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752543AbdDQJOk (ORCPT ); Mon, 17 Apr 2017 05:14:40 -0400 In-Reply-To: Sender: linux-crypto-owner@vger.kernel.org List-ID: 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