From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753213AbbF3O2s (ORCPT ); Tue, 30 Jun 2015 10:28:48 -0400 Received: from casper.infradead.org ([85.118.1.10]:55039 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752899AbbF3O2l (ORCPT ); Tue, 30 Jun 2015 10:28:41 -0400 Date: Tue, 30 Jun 2015 16:28:33 +0200 From: Peter Zijlstra To: Oleg Nesterov Cc: Tejun Heo , paulmck@linux.vnet.ibm.com, mingo@redhat.com, der.herr@hofr.at, dave@stgolabs.net, riel@redhat.com, viro@ZenIV.linux.org.uk, torvalds@linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 4/5] stop_machine: use cpu_stop_fn_t where possible Message-ID: <20150630142833.GI3644@twins.programming.kicks-ass.net> References: <20150630012931.GA23904@redhat.com> <20150630012955.GA23937@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150630012955.GA23937@redhat.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 30, 2015 at 03:29:55AM +0200, Oleg Nesterov wrote: > Cosmetic, but cpu_stop_fn_t actually makes the code more readable and > it doesn't break cscope. And most of the declarations already use it. I made that cpu_stop_f