From: Thomas Gleixner <tglx@linutronix.de>
To: Simon Horman <horms@verge.net.au>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
benh@kernel.crashing.org, grant.likely@secretlab.ca
Subject: Re: [PATCH] irqchip: Renesas INTC External IRQ pin driver
Date: Wed, 6 Mar 2013 14:05:52 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1303061405200.22263@ionos> (raw)
In-Reply-To: <20130306114622.GE6684@verge.net.au>
On Wed, 6 Mar 2013, Simon Horman wrote:
> On Wed, Mar 06, 2013 at 11:01:14AM +0100, Thomas Gleixner wrote:
> > On Wed, 6 Mar 2013, Simon Horman wrote:
> > > On Mon, Feb 18, 2013 at 11:28:34PM +0900, Magnus Damm wrote:
> > > > The SoCs using this driver are currently mainly used
> > > > together with regular platform devices so this driver
> > > > allows configuration via platform data to support things
> > > > like static interrupt base address. DT support will
> > > > be added incrementally in the not so distant future.
> > >
> > > Hi Thomas,
> > >
> > > I'm wondering how you would like to handle merging this driver.
> > > I can think of three options but I'm sure there are others.
> > >
> > > * You can take the patches (there is a follow-up series) yourself.
> > > * I can prepare a pull request for you
> > > * I can prepare a pull request for arm-soc with the shmobile patches that
> > > enable the driver on the r8a7779 and sh73a0.
> > >
> > > The last option is possibly the easiest.
> >
> > Correct.
> >
> > > But in that case I'd appreciate an Ack from you on this patch.
> >
> > You want to pick the V2 series, which already has my blessing:
> >
> > https://lkml.org/lkml/2013/2/26/305
> >
> > For merging it through arm-soc you have my ack now :)
>
> Thanks, I have that.
>
> It seems that V2 adds onto this patch rather than replaces it.
> So could I also get an Ack for this patch too?
Ah,. right. V2 is an incremental fix for V1. Yes, please add my Ack.
Thanks,
tglx
next prev parent reply other threads:[~2013-03-06 13:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 14:28 [PATCH] irqchip: Renesas INTC External IRQ pin driver Magnus Damm
2013-02-19 1:03 ` Simon Horman
2013-02-19 10:30 ` Magnus Damm
2013-02-19 1:04 ` Kuninori Morimoto
2013-02-19 10:38 ` Magnus Damm
2013-02-19 10:11 ` Thomas Gleixner
2013-02-19 10:58 ` Magnus Damm
2013-02-19 13:14 ` Thomas Gleixner
2013-02-27 8:23 ` Paul Mundt
2013-02-27 8:35 ` Magnus Damm
2013-02-27 8:52 ` Paul Mundt
2013-02-27 9:52 ` Magnus Damm
2013-02-27 10:28 ` Paul Mundt
2013-03-06 7:36 ` Magnus Damm
2013-03-06 4:23 ` Simon Horman
2013-03-06 10:01 ` Thomas Gleixner
2013-03-06 11:46 ` Simon Horman
2013-03-06 13:05 ` Thomas Gleixner [this message]
2013-03-08 7:25 ` Simon Horman
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=alpine.LFD.2.02.1303061405200.22263@ionos \
--to=tglx@linutronix.de \
--cc=benh@kernel.crashing.org \
--cc=grant.likely@secretlab.ca \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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