[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200227110713.GA5708@afzalpc>
Date: Thu, 27 Feb 2020 16:37:13 +0530
From: afzal mohammed <afzal.mohd.ma@...il.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: linux-kernel@...r.kernel.org, linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, x86@...nel.org,
linux-sh@...r.kernel.org, linux-s390@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-parisc@...r.kernel.org,
linux-mips@...r.kernel.org, linux-m68k@...ts.linux-m68k.org,
linux-ia64@...r.kernel.org, linux-hexagon@...r.kernel.org,
linux-c6x-dev@...ux-c6x.org, linux-omap@...r.kernel.org,
linux-alpha@...r.kernel.org, Julia Lawall <Julia.Lawall@...6.fr>,
Gilles Muller <Gilles.Muller@...6.fr>,
Nicolas Palix <nicolas.palix@...g.fr>,
Michal Marek <michal.lkml@...kovi.net>
Subject: Re: [PATCH 00/18] genirq: Remove setup_irq()
Hi Thomas,
On Thu, Feb 27, 2020 at 11:31:15AM +0100, Thomas Gleixner wrote:
> Vs. merging this series, I suggest the following approach:
>
> - Resubmit the individual changes as single patches or small series
> to the relevant maintainers and subsystem mailing lists. They have
> no dependency on a core change and can be applied where they belong
> to.
>
> - After 5.6-rc6, verify which parts have made their way into
> linux-next and resubmit the ignored ones as a series to me along
> with the removal of the core parts.
>
> That way we can avoid conflicting changes between subsystems and the tip
> irq/core branch as much as possible.
Okay, i will do accordingly.
[ your mail crossed my v3 (only one patch) posting ]
Regards
afzal
Powered by blists - more mailing lists