From: Thomas Gleixner <tglx@linutronix.de>
To: Grant Likely <grant.likely@linaro.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Try out the irqdomain + generic chip integration series
Date: Wed, 29 May 2013 10:19:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1305291017070.2995@ionos> (raw)
In-Reply-To: <1369793454-19197-1-git-send-email-grant.likely@linaro.org>
Grant,
On Wed, 29 May 2013, Grant Likely wrote:
> Hi Thomas,
>
> Rather than just straight reviewing the generic irq chip patch series, I
> tried it out by converting another driver to use it. As far as I've been
> able to tell it does the right thing and you can have my ack. The first
> patch in this series adds another feature needed by the versatile
> driver. Patch 2 should be okay, but I'd like to get an ack from Ben
> before it gets applied.
I pick up #1 and push it with the other lot, so people can start
working on top of that. I'll put it into a separate branch
(irq/for-arm) so SoC folks can grab it from there to avoid inter tree
dependencies.
> I need to get someone to test patch 3 on hardware before you pick up
> that one.
Sure. It might also go through the SoC tree(s).
> Oh, and I'll reply directly to patch 7 of your series with an ack and a
> minor comment.
Thanks,
tglx
prev parent reply other threads:[~2013-05-29 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 2:10 Grant Likely
2013-05-29 2:10 ` [PATCH 1/3] irqchip: Add mask to block out invalid irqs Grant Likely
2013-05-29 9:23 ` [tip:irq/core] genirq: " tip-bot for Grant Likely
2013-05-29 2:10 ` [PATCH 2/3] irqdomain: Relax failure path on setting up mappings Grant Likely
2013-05-29 2:10 ` [PATCH 3/3] irqchip: Make versatile fpga irq driver a generic chip Grant Likely
2013-05-29 17:55 ` Linus Walleij
2013-05-29 19:56 ` Grant Likely
2013-05-30 21:06 ` Linus Walleij
2013-05-29 8:19 ` Thomas Gleixner [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=alpine.LFD.2.02.1305291017070.2995@ionos \
--to=tglx@linutronix.de \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®