From: Eric Anholt <eric@anholt.net>
To: linux-rpi-kernel@lists.infradead.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>,
Eric Anholt <eric@anholt.net>
Subject: [PATCH 0/4] irqchip: bcm2835: arm64 port
Date: Mon, 4 Apr 2016 20:44:14 -0700 [thread overview]
Message-ID: <1459827858-3871-1-git-send-email-eric@anholt.net> (raw)
Here's the series for irqchip-bcm283x on arm64 for the Pi3. Since I'd
like to land Makefile changes that would enable building
irqchip-bcm283x on arm64, it would be nice if I had either a stable
branch to merge from, or an ack to merge them through the arm64 tree.
Eric Anholt (4):
irqchip: bcm2835: Avoid arch/arm-specific handle_IRQ
irqchip: bcm2836: Drop smp_set_ops on arm64 builds
irqchip: bcm2836: Fix compiler warning on 64-bit build
irqchip: bcm2836: Use a more generic memory barrier call
drivers/irqchip/irq-bcm2835.c | 3 +--
drivers/irqchip/irq-bcm2836.c | 12 ++++++++----
2 files changed, 9 insertions(+), 6 deletions(-)
--
2.7.0
next reply other threads:[~2016-04-05 3:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 3:44 Eric Anholt [this message]
2016-04-05 3:44 ` [PATCH 1/4] irqchip: bcm2835: Avoid arch/arm-specific handle_IRQ Eric Anholt
2016-04-05 3:44 ` [PATCH 2/4] irqchip: bcm2836: Drop smp_set_ops on arm64 builds Eric Anholt
2016-04-05 13:44 ` Marc Zyngier
2016-04-08 20:43 ` Arnd Bergmann
2016-04-13 19:49 ` Eric Anholt
2016-04-05 3:44 ` [PATCH 3/4] irqchip: bcm2836: Fix compiler warning on 64-bit build Eric Anholt
2016-04-05 3:44 ` [PATCH 4/4] irqchip: bcm2836: Use a more generic memory barrier call Eric Anholt
2016-04-06 4:59 ` Stephen Warren
2016-04-08 18:20 ` Eric Anholt
2016-04-09 5:26 ` Stephen Warren
2016-04-10 18:32 ` Eric Anholt
2016-04-11 15:52 ` Stephen Warren
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=1459827858-3871-1-git-send-email-eric@anholt.net \
--to=eric@anholt.net \
--cc=jason@lakedaemon.net \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=swarren@wwwdotorg.org \
--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®