From: Jason Cooper <jason@lakedaemon.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Gregory CLEMENT <gregory.clement@free-electrons.com>,
Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>,
linux-kernel@vger.kernel.org,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL V2] irqchip: mvebu fixes for v3.14
Date: Fri, 21 Feb 2014 17:03:30 -0500 [thread overview]
Message-ID: <20140221220330.GN7862@titan.lakedaemon.net> (raw)
In-Reply-To: <20140218162210.GU7862@titan.lakedaemon.net>
Thomas,
Here it is. Sorry for the delay. I was under the weather past couple
days.
thx,
Jason.
The following changes since commit 38dbfb59d1175ef458d006556061adeaa8751b72:
Linus 3.14-rc1 (2014-02-02 16:42:13 -0800)
are available in the git repository at:
git://git.infradead.org/linux-mvebu.git tags/irqchip-mvebu-fixes-3.14
for you to fetch changes up to d86e9af6336c0ad586a5dbd70064253d40bbb5ff:
irqchip: orion: Fix getting generic chip pointer. (2014-02-21 21:46:56 +0000)
----------------------------------------------------------------
irqchip mvebu fixes for v3.14
- orion:
- fixes for clearing bridge cause register, and clearing stale interrupts
----------------------------------------------------------------
Andrew Lunn (1):
irqchip: orion: Fix getting generic chip pointer.
Sebastian Hesselbarth (3):
irqchip: orion: clear bridge cause register on init
irqchip: orion: use handle_edge_irq on bridge irqs
irqchip: orion: clear stale interrupts in irq_startup
drivers/irqchip/irq-orion.c | 22 +++++++++++++++++++---
1 file changed, 19 insertions(+), 3 deletions(-)
prev parent reply other threads:[~2014-02-21 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 16:22 [GIT PULL] " Jason Cooper
2014-02-18 20:23 ` Thomas Gleixner
2014-02-19 15:35 ` Jason Cooper
2014-02-21 22:03 ` Jason Cooper [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=20140221220330.GN7862@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.hesselbarth@googlemail.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
all inboxes | Powered by JetHome®