From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Marvell Armada 375/38x MPIC/MSI fixes
Date: Tue, 21 Oct 2014 11:19:31 -0300 [thread overview]
Message-ID: <54466B73.3090704@free-electrons.com> (raw)
In-Reply-To: <20141003135017.GH3895@titan.lakedaemon.net>
On 10/03/2014 10:50 AM, Jason Cooper wrote:
> On Thu, Sep 25, 2014 at 01:17:17PM +0200, Grzegorz Jaszczyk wrote:
>> This patchset contains a set of fixes for issues found while doing some test
>> with different interrupts configuration on Armada 375 and Armada 38x Marvell
>> SoCs. The patches were tested and apply on v3.17-rc6.
>>
>> Any feedback is welcome.
>>
>> Grzegorz Jaszczyk (2):
>> irqchip: armada-370-xp: fix MSI interrupt handling
>> irqchip: armada-370-xp: fix MPIC interrupt handling
>>
>> drivers/irqchip/irq-armada-370-xp.c | 23 +++++++++++++++++------
>> 1 file changed, 17 insertions(+), 6 deletions(-)
>
> Ah crap. This slipped off my plate. Sorry about that. I've now
> applied these to irqchip/urgent with Ezequiel's Ack. I'll get them into
> -next and hopefully do a PR toward the end of next week.
>
Jason,
The patches don't seem to be in v3.18-rc1 for some reason.
I can't seem to find your PR (probably because I've switched to
Thunderbird now
and it's a pain to search mails properly).
Since this is an important fix, maybe you can schedule it for -rc2?
Thanks!
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-21 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1411643839-64925-1-git-send-email-jaz@semihalf.com>
2014-09-25 21:56 ` [PATCH 0/2] Marvell Armada 375/38x MPIC/MSI fixes Ezequiel Garcia
2014-10-03 13:50 ` Jason Cooper
2014-10-21 14:19 ` Ezequiel Garcia [this message]
2014-10-21 15:14 ` Jason Cooper
2014-10-21 21:22 ` Ezequiel Garcia
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=54466B73.3090704@free-electrons.com \
--to=ezequiel.garcia@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).