From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 5/4] Broadcom soc-arm64 changes for 4.8 part 2
Date: Thu, 07 Jul 2016 15:58:34 +0200 [thread overview]
Message-ID: <3314738.osW38YoyUP@wuerfel> (raw)
In-Reply-To: <1467867851-11298-1-git-send-email-f.fainelli@gmail.com>
On Wednesday, July 6, 2016 10:04:11 PM CEST Florian Fainelli wrote:
> This pull requests contains Broadcom ARM64-based SoC changes for 4.8 second part:
>
> - Eric updates the bcm2836 interrupt controller driver not to rely on ARM/Linux specific functions
> in preparation for using it on ARM64
>
> - Eric also adds a Kconfig entry for the BCM2835 Raspberry Pi family in the ARM64 Kconfig.platforms
> file
>
> - Eric cherry picked a patch from Alexander Graf with Acks from ARM64 maintainers to support different
> DMA and bus offsets, required for the Raspberry Pi 3 SoC
>
>
Pulled into next/arm64, thanks!
Arnd
next prev parent reply other threads:[~2016-07-07 13:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 3:36 [GIT PULL 0/4] Second round of Broadcom changes for 4.8 Florian Fainelli
2016-07-07 3:36 ` [GIT PULL 3/4] Broadcom ARM64 Device Tree changes for 4.8 (part 2) Florian Fainelli
2016-07-07 13:50 ` Arnd Bergmann
2016-07-07 3:36 ` [GIT PULL 1/4] Broadcom ARM devicetree " Florian Fainelli
2016-07-07 13:33 ` Arnd Bergmann
2016-07-07 3:36 ` [GIT PULL 4/4] Broadcom MAINTAINERS file updates for 4.8 (resend) Florian Fainelli
2016-07-07 13:53 ` Arnd Bergmann
2016-07-07 3:36 ` [GIT PULL 2/4] Broadcom ARM-based SoC changes for 4.8 (part 2) Florian Fainelli
2016-07-07 13:41 ` Arnd Bergmann
2016-07-07 5:04 ` [GIT PULL 5/4] Broadcom soc-arm64 changes for 4.8 part 2 Florian Fainelli
2016-07-07 13:58 ` Arnd Bergmann [this message]
2016-07-07 5:05 ` [GIT PULL 0/4] Second round of Broadcom changes for 4.8 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=3314738.osW38YoyUP@wuerfel \
--to=arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.