From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757214AbdDQJOn (ORCPT ); Mon, 17 Apr 2017 05:14:43 -0400 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 Date: Mon, 17 Apr 2017 11:14:23 +0200 (CEST) From: Thomas Gleixner To: "Jason A. Donenfeld" cc: LKML , Peter Zijlstra , Ingo Molnar , Steven Rostedt , Sebastian Siewior , Steffen Klassert , Linux Crypto Mailing List Subject: Re: [patch 03/20] padata: Make padata_alloc() static In-Reply-To: Message-ID: References: <20170415170107.643253702@linutronix.de> <20170415171651.483363066@linutronix.de> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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