From: Jason Cooper <jason@lakedaemon.net>
To: Eric Anholt <eric@anholt.net>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>
Subject: Re: [GIT PULL 3/3] bcm2835-arm64-next-2016-07-03
Date: Tue, 5 Jul 2016 18:03:38 +0000 [thread overview]
Message-ID: <20160705180338.GI3348@io.lakedaemon.net> (raw)
In-Reply-To: <1467593136-29524-4-git-send-email-eric@anholt.net>
Eric,
On Sun, Jul 03, 2016 at 05:45:36PM -0700, Eric Anholt wrote:
> Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
>
> are available in the git repository at:
>
> https://github.com/anholt/linux tags/bcm2835-arm64-next-2016-07-03
>
> for you to fetch changes up to 628d30d1ccb897fee54a6f7312561cf2f6f72f09:
>
> arm64: Add platform selection for BCM2835. (2016-06-15 14:10:30 -0700)
>
> ----------------------------------------------------------------
> This pull request brings in the build support for the Raspberry Pi
> arm64 port.
>
> ----------------------------------------------------------------
> Alexander Graf (1):
> arm64: Allow for different DMA and CPU bus offsets
>
> Eric Anholt (3):
> irqchip: bcm2835: Avoid arch/arm-specific handle_IRQ
> Merge remote-tracking branch 'irqchip/irqchip/bcm' into bcm2835-arm64-next
You may want to draw attention to the fact that this has an external
dependency on my irqchip/bcm branch. Also, that it's stable, been in
-next for a couple of weeks, and based on v4.7-rc1, etc.
thx,
Jason.
> arm64: Add platform selection for BCM2835.
>
> arch/arm64/Kconfig.platforms | 13 +++++++++++++
> arch/arm64/include/asm/dma-mapping.h | 17 +++++++++++++++--
> drivers/irqchip/irq-bcm2835.c | 3 +--
> drivers/irqchip/irq-bcm2836.c | 2 +-
> 4 files changed, 30 insertions(+), 5 deletions(-)
next prev parent reply other threads:[~2016-07-05 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 0:45 [GIT PULL 0/3] BCM2835 pull requests for 4.8 Eric Anholt
2016-07-04 0:45 ` [GIT PULL 1/3] bcm2835-dt-next-2016-07-03 Eric Anholt
2016-07-06 3:46 ` Florian Fainelli
2016-07-04 0:45 ` [GIT PULL 2/3] bcm2835-dt-64-next-2016-07-03 Eric Anholt
2016-07-06 3:48 ` Florian Fainelli
2016-07-04 0:45 ` [GIT PULL 3/3] bcm2835-arm64-next-2016-07-03 Eric Anholt
2016-07-05 18:03 ` Jason Cooper [this message]
2016-07-06 3:50 ` Florian Fainelli
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=20160705180338.GI3348@io.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--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=swarren@wwwdotorg.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®