From: stigge@antcom•de (Roland Stigge)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] lpc32xx: irq - Set the chain handlers after setting up the IRQ domain
Date: Mon, 05 Nov 2012 18:35:54 +0100 [thread overview]
Message-ID: <5097F8FA.6040605@antcom.de> (raw)
In-Reply-To: <20121105180053.20090a3e@avionic-0020.adnet.avionic-design.de>
Hi!
On 05/11/12 18:00, Alban Bedel wrote:
>> I already posted basically the same change on 2012-10-28 already which
>> is part of my patch set for LPC32xx to be merged into arm-soc.git (will
>> do a pull request later). Fixing another irq bug in this platform/irq also.
>
> I checked arm-soc.git, linux-next.git, linux-arm-kernel@ and
> linux-kernel@, is there any other place I should check before
> submitting LPC32xx patches?
I usually prepare lpc32xx branches for merging into arm-soc.git at
git.antcom.de. Expect the posted patches there and a pull request during
the next days.
Thanks,
Roland
prev parent reply other threads:[~2012-11-05 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 12:23 [PATCH] lpc32xx: irq - Set the chain handlers after setting up the IRQ domain Alban Bedel
2012-11-02 9:01 ` Roland Stigge
2012-11-05 17:00 ` Alban Bedel
2012-11-05 17:35 ` Roland Stigge [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=5097F8FA.6040605@antcom.de \
--to=stigge@antcom$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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