From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <1325854981.2442.25.camel@twins> Subject: Re: [RFC PATCH 0/9] Remove useless on_each_cpu return value From: Peter Zijlstra To: Gilad Ben-Yossef Date: Fri, 06 Jan 2012 14:03:01 +0100 In-Reply-To: <1325600353-10895-1-git-send-email-gilad@benyossef.com> References: <1325600353-10895-1-git-send-email-gilad@benyossef.com> Content-Type: text/plain; charset="ISO-8859-1" Mime-Version: 1.0 Cc: linux-ia64@vger.kernel.org, David Airlie , Will Deacon , dri-devel@lists.freedesktop.org, Paul Mackerras , "H. Peter Anvin" , Russell King , x86@kernel.org, Ingo Molnar , Arnaldo Carvalho de Melo , Matt Turner , Fenghua Yu , devicetree-discuss@lists.ozlabs.org, Michal Nazarewicz , Ivan Kokshaysky , Rob Herring , Thomas Gleixner , linux-arm-kernel@lists.infradead.org, Richard Henderson , Tony Luck , linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org, linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 2012-01-03 at 16:19 +0200, Gilad Ben-Yossef wrote: > on_each_cpu() returns as its own return value the return value of=20 > smp_call_function(). smp_call_function() in turn returns a hard=20 > coded value of zero. >=20 > Some callers to on_each_cpu() waste cycles and bloat code space > by checking the return value to on_each_cpu(), probably for=20 > historical reasons. hysterical raisins,, yumm! :-) > This patch set refactors callers to not test on_each_cpu() > (fixed) return value and then refactors on_each_cpu to > return void to avoid confusing future users. >=20 Seems sane enough, fwiw: Acked-by: Peter Zijlstra