From: hauke@hauke-m.de (Hauke Mehrtens)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2] ARM: BCM5301X: DT changes for v3.19
Date: Thu, 27 Nov 2014 22:37:29 +0100 [thread overview]
Message-ID: <54779999.8020709@hauke-m.de> (raw)
Hi Olof, Hi Arnd,
Please consider these BCM5301X ARM based SoC dt updates for v3.19.
This is the second try based on 3.18-rc1 and without the early printk patch.
The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
are available in the git repository at:
https://github.com/hauke/linux.git tags/bcm5301x-dt-2014-11-27
for you to fetch changes up to dd6d2e5f4bbb828268506e9d6b772fffe101e76c:
ARM: BCM5301X: Add LEDs for Netgear R6250 V1 (2014-11-27 22:30:32 +0100)
----------------------------------------------------------------
ARM: BCM5301X: Add some more devices to device tree
The most important part is adding the axi bus to the SoC dtsi file,
this is the main bus on the SoC.
These patches were all send to the arm list and I haven't got any
negative responses.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
----------------------------------------------------------------
Rafa? Mi?ecki (2):
ARM: BCM5301X: Add Broadcom's bus-axi to the DTS file
ARM: BCM5301X: Add LEDs for Netgear R6250 V1
arch/arm/boot/dts/bcm4708-netgear-r6250.dts | 34
+++++++++++++++++++++++++++++
arch/arm/boot/dts/bcm5301x.dtsi | 16 ++++++++++++++
2 files changed, 50 insertions(+)
next reply other threads:[~2014-11-27 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 21:37 Hauke Mehrtens [this message]
2014-11-28 21:40 ` [GIT PULL v2] ARM: BCM5301X: DT changes for v3.19 Arnd Bergmann
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=54779999.8020709@hauke-m.de \
--to=hauke@hauke-m.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.