From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752891AbcKSLpW (ORCPT ); Sat, 19 Nov 2016 06:45:22 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:60779 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752499AbcKSLpV (ORCPT ); Sat, 19 Nov 2016 06:45:21 -0500 Date: Sat, 19 Nov 2016 12:45:11 +0100 From: Peter Zijlstra To: "Reshetova, Elena" Cc: "gregkh@linuxfoundation.org" , "keescook@chromium.org" , "will.deacon@arm.com" , "arnd@arndb.de" , "tglx@linutronix.de" , "mingo@kernel.org" , "hpa@zytor.com" , "dave@progbits.org" , "linux-kernel@vger.kernel.org" Subject: Re: [RFC][PATCH 7/7] kref: Implement using refcount_t Message-ID: <20161119114511.GG11311@worktop.programming.kicks-ass.net> References: <20161114173946.501528675@infradead.org> <20161114174446.832175072@infradead.org> <2236FBA76BA1254E88B949DDB74E612B41C14924@IRSMSX102.ger.corp.intel.com> <20161118105206.GM3117@twins.programming.kicks-ass.net> <2236FBA76BA1254E88B949DDB74E612B41C14B3B@IRSMSX102.ger.corp.intel.com> <20161118185351.GW3117@twins.programming.kicks-ass.net> <2236FBA76BA1254E88B949DDB74E612B41C14F79@IRSMSX102.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2236FBA76BA1254E88B949DDB74E612B41C14F79@IRSMSX102.ger.corp.intel.com> User-Agent: Mutt/1.5.22.1 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Nov 19, 2016 at 07:14:08AM +0000, Reshetova, Elena wrote: > > Well, if you get to tools (cocci script or whatever) to reliably work > > fork atomic_t, then converting the few atomic_long_t's later should be > > trivial. > > I am using coccinelle to find all occurrences, but I do the changes > only in semi-automated fashion. If you can get the detection solid, that's good enough. > Each change needs a proper manual review anyway and often one variable > usage is spread between different headers/source files, so I prefer > not to go to full automation and then not being sure what I have done. Sure, every patch needs review, regardless of how it came to be.