From: Jason Cooper <jason@lakedaemon.net>
To: Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] irqchip: Fixes for v4.0
Date: Sun, 15 Mar 2015 03:00:11 +0000 [thread overview]
Message-ID: <20150315030011.GF4463@io.lakedaemon.net> (raw)
Thomas,
Here's a round of fixes for v4.0. They've been in -next for a week without
issue. Please pull.
Linus,
I've heard that Thomas isn't available. I have no other specifics. If you
know his absence is going to last for a while, please consider pulling this
directly. I'd hate to miss getting these fixes in.
thx,
Jason.
The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
are available in the git repository at:
git://git.infradead.org/users/jcooper/linux.git tags/irqchip-fixes-4.0
for you to fetch changes up to aaa95f74563a1c5a42db5fec43415b9a92ea7f7b:
Merge branch 'irqchip/urgent-gic' into irqchip/urgent (2015-03-15 01:41:26 +0000)
----------------------------------------------------------------
irqchip fixes for v4.0
- armada-370-xp
- Chained per-cpu interrupts
- gic{,-v3,v3-its}
- Various fixes for safer operation
----------------------------------------------------------------
Jason Cooper (1):
Merge branch 'irqchip/urgent-gic' into irqchip/urgent
Marc Zyngier (4):
irqchip: gicv3-its: Allocate enough memory for the full range of DeviceID
irqchip: gicv3-its: Iterate over PCI aliases to generate ITS configuration
irqchip: gicv3-its: Fix unsafe locking reported by lockdep
irqchip: gic: Fix unsafe locking reported by lockdep
Maxime Ripard (1):
irqchip: armada-370-xp: Fix chained per-cpu interrupts
Vladimir Murzin (2):
irqchip: gicv3-its: Fix ITS CPU init
irqchip: gic-v3: Fix out of bounds access to cpu_logical_map
Yun Wu (5):
irqchip: gicv3-its: Zero itt before handling to hardware
irqchip: gicv3-its: Use 64KB page as default granule
irqchip: gicv3-its: Add limitation to page order
irqchip: gicv3-its: Define macros for GITS_CTLR fields
irqchip: gicv3-its: Support safe initialization
drivers/irqchip/irq-armada-370-xp.c | 21 ++++-
drivers/irqchip/irq-gic-v3-its.c | 157 +++++++++++++++++++++++++++++-------
drivers/irqchip/irq-gic-v3.c | 2 +-
drivers/irqchip/irq-gic.c | 20 +++--
include/linux/irqchip/arm-gic-v3.h | 5 ++
5 files changed, 166 insertions(+), 39 deletions(-)
reply other threads:[~2015-03-15 3:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150315030011.GF4463@io.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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®