Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753764AbbGBSeb (ORCPT ); Thu, 2 Jul 2015 14:34:31 -0400 Received: from mail-yk0-f174.google.com ([209.85.160.174]:32781 "EHLO mail-yk0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753595AbbGBSeX convert rfc822-to-8bit (ORCPT ); Thu, 2 Jul 2015 14:34:23 -0400 MIME-Version: 1.0 In-Reply-To: <5241045.u2d8ixKRcE@joel-zenbook> References: <1435790000-15720-1-git-send-email-joel@porquet.org> <5594E229.2020506@synopsys.com> <5241045.u2d8ixKRcE@joel-zenbook> Date: Thu, 2 Jul 2015 20:34:22 +0200 Message-ID: Subject: Re: [PATCH 00/48] Make the IRQCHIP_DECLARE macro globally accessible From: Matthias Brugger To: =?UTF-8?Q?Jo=C3=ABl_Porquet?= Cc: Vineet Gupta , Russell King , Kukjin Kim , =?UTF-8?Q?Krzysztof_Koz=C5=82owski?= , Shawn Guo , "=Sascha Hauer" , Tony Lindgren , monstr@monstr.eu, cernekee@gmail.com, Florian Fainelli , ralf@linux-mips.org, Thomas Gleixner , Jason Cooper , swarren@wwwdotorg.org, lee@kernel.org, shc_work@mail.ru, baruch@tkos.co.il, Barry Song , Maxime Ripard , Thierry Reding , gnurou@gmail.com, chris@zankel.net, jcmvbkbc@gmail.com, =?UTF-8?Q?S=C3=B6ren_Brinkmann?= , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2876 Lines: 66 2015-07-02 20:23 GMT+02:00 Joël Porquet : > On Thursday, July 02, 2015 12:33:05 PM Vineet Gupta wrote: >> On Thursday 02 July 2015 04:02 AM, Joel Porquet wrote: >> > At the moment the IRQCHIP_DECLARE macro is only declared locally in >> > 'drivers/irqchip/irqchip.h'. That prevents from using it directly in >> > arch/* >> > directories whenever irqchip drivers only exist there, which happens in a >> > few cases (e.g. arc, arm, microblaze and mips). >> > >> > This patch makes the macro to be globally defined, in >> > include/linux/irqchip.h, and thus usable for arch-specific declarations >> > of irqchip drivers. In this way, it is very similar to what clocksource >> > does (ie CLOCKSOURCE_OF_DECLARE is defined in >> > include/linux/clocksource.h). >> > >> > I split up everything into patches to make the integration easier. Please >> > let me know if it's not, and in such case how to make it better. >> > >> > For now, patch 01 of this series transfers the declaration of the macro >> > IRQCHIP_DECLARE to the global header 'include/linux/irqchip.h'. The >> > following patches, from 02 to 47, modify all the irqchip drivers that use >> > IRQCHIP_DECLARE, one by one. And finally, the last patch 48 removes the >> > private and now useless header 'drivers/irqchip/irqchip.h'. >> >> Hi Joel, >> >> I don't see the rest of series on lkml and/or the patch which touches >> arch/arc. Also, you may wanna redo this after 4.2-rc1 anyways. For ARC >> atleast, there's a new intc which would also require similar fixup. There >> might be others .... >> >> Thx, >> -Vineet > > Hi Vineet (and all), > > Sorry for the mistake, I hope I didn't spam anyone (too much). I realized to > late that sending about fifty patches to 26 recipients was probably not a good > idea, and my smtp provider would have blocked me before the end anyway. > > Therefore I will follow your suggestion and wait until after 4.2-rc1. Then > I'll resubmit a new patchset that takes into account the new intc(s) as well. > > But since this patchset affects many files across several drivers and > architectures, what would be the best way to submit it? > > Would it be OK to send the cover to all the maintainers/mailing-lists involved > in order to inform them that a patchset is affecting their respective > subsystem, but to send the patches only on the kernel mailing-list? What I have seen recently is, that you send to each maintainer the cover letter and the patch he is concerned about. And put the kernel maling-list(s) in all patches as CC. Please anyone correct me if I'm wrong. Regrads, Matthias -- motzblog.wordpress.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/