From: Simon Horman <horms@verge.net.au>
To: Thomas Gleixner <tglx@linutronix.de>
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: Fri, 8 Mar 2013 08:25:09 +0100 [thread overview]
Message-ID: <20130308072508.GA13457@verge.net.au> (raw)
In-Reply-To: <alpine.LFD.2.02.1303061405200.22263@ionos>
On Wed, Mar 06, 2013 at 02:05:52PM +0100, Thomas Gleixner wrote:
> 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.
I have added this into a new intc-external-irq branch of
the renesas tree on kernel.org and thus queued it up for v3.10.
I have also added the following patches to that branch:
irqchip: irqc: Add DT support
irqchip: intc-irqpin: Initial DT support
ARM: shmobile: Make r8a7779 INTC irqpin platform data static
ARM: shmobile: Make sh73a0 INTC irqpin platform data static
irqchip: Renesas IRQC driver
irqchip: intc-irqpin: GPL header for platform data
irqchip: intc-irqpin: Make use of devm functions
irqchip: intc-irqpin: Add force comments
irqchip: intc-irqpin: Cache mapped IRQ
irqchip: intc-irqpin: Whitespace fixes
ARM: shmobile: INTC External IRQ pin driver on r8a7779
ARM: shmobile: INTC External IRQ pin driver on sh73a0
ARM: shmobile: irq_pin() for static IRQ pin assignment
The intc-external-irq branch is merged into the next branch and
I expect it to appear in linux-next in the not to distant future.
I have removed the topic/intc-external-irq branch from the reneas tree,
the branch where these patches were being staged.
prev parent reply other threads:[~2013-03-08 7:25 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
2013-03-08 7:25 ` Simon Horman [this message]
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=20130308072508.GA13457@verge.net.au \
--to=horms@verge.net.au \
--cc=benh@kernel.crashing.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=tglx@linutronix.de \
/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