From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 20 May 2015 22:22:38 +0200 (CEST) From: Thomas Gleixner To: Julia Lawall cc: Jiang Liu , Bjorn Helgaas , Benjamin Herrenschmidt , Ingo Molnar , "H. Peter Anvin" , "Rafael J. Wysocki" , Randy Dunlap , Yinghai Lu , Borislav Petkov , Jason Cooper , Kevin Cernekee , Arnd Bergmann , Marc Zyngier , Konrad Rzeszutek Wilk , Tony Luck , x86@kernel.org, LKML , linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org Subject: Re: [RFC v1 14/25] genirq: Kill the first parameter 'irq' of irq_flow_handler_t In-Reply-To: Message-ID: References: <1432116013-25902-1-git-send-email-jiang.liu@linux.intel.com> <1432116013-25902-15-git-send-email-jiang.liu@linux.intel.com> <555CA834.7080807@linux.intel.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-acpi-owner@vger.kernel.org List-ID: On Wed, 20 May 2015, Julia Lawall wrote: > On Wed, 20 May 2015, Thomas Gleixner wrote: > > On Wed, 20 May 2015, Julia Lawall wrote: > > > Scripting this may be a little complex, because the variable can be used > > > in one way in one execution path (eg if branch) and another way (or not at > > > all) in another. Let me know if help is needed. > > > > I feared that, but at least identifying all functions, where the irq > > argument is used inside the function itself is really key for such a > > massive rework. > > It's not impossible, but I may need to think a bit how best to do it. I pretty much expected that you would say that :) But seriously, the first important thing is to find all functions and to check whether they use irq internaly. Jiang has done that 'manually' or such, so the number of function which need an actual change are not that big. But I certainly don't want to hold you off thinking about it. Such stuff is not a unique problem :) tglx