From: afzal mohammed <afzal.mohd.ma@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-s390@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-ia64@vger.kernel.org, linux-c6x-dev@linux-c6x.org,
linux-parisc@vger.kernel.org, linux-sh@vger.kernel.org,
linux-hexagon@vger.kernel.org, x86@kernel.org,
Nicolas Palix <nicolas.palix@imag.fr>,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
Julia Lawall <Julia.Lawall@lip6.fr>,
linux-m68k@lists.linux-m68k.org,
Michal Marek <michal.lkml@markovi.net>,
linux-rpi-kernel@lists.infradead.org,
linux-alpha@vger.kernel.org,
Gilles Muller <Gilles.Muller@lip6.fr>,
linux-omap@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/18] genirq: Remove setup_irq()
Date: Sat, 21 Mar 2020 23:13:03 +0530 [thread overview]
Message-ID: <20200321174303.GA7930@afzalpc> (raw)
In-Reply-To: <20200227110713.GA5708@afzalpc>
Hi Thomas,
On Thu, Feb 27, 2020 at 04:37:13PM +0530, afzal mohammed wrote:
> 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.
i am on it, is delayed due to the reason as mentioned at,
https://lkml.kernel.org/r/20200321172626.GA6323@afzalpc
[ not repeating contents here since other mail was sent just now,
cc'ing you ]
Regards
afzal
next prev parent reply other threads:[~2020-03-21 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 8:01 [PATCH 00/18] genirq: Remove setup_irq() afzal mohammed
2020-02-12 8:04 ` [PATCH 10/18] powerpc: Replace setup_irq() by request_irq() afzal mohammed
2020-02-13 10:59 ` Christophe Leroy
2020-02-27 10:31 ` [PATCH 00/18] genirq: Remove setup_irq() Thomas Gleixner
2020-02-27 11:07 ` afzal mohammed
2020-03-21 17:43 ` afzal mohammed [this message]
2020-03-27 16:08 ` [PATCH 0/6] Kill setup_irq() afzal mohammed
2020-03-28 2:48 ` Brian Cain
2020-03-28 7:32 ` afzal mohammed
2020-04-02 15:03 ` Brian Cain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200321174303.GA7930@afzalpc \
--to=afzal.mohd.ma@gmail.com \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).