From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/9] ARM: bcm283x: RPi 3 B+ support and other improvements
Date: Mon, 23 Apr 2018 18:02:33 -0700 [thread overview]
Message-ID: <87zi1to1qu.fsf@anholt.net> (raw)
In-Reply-To: <1524310122-9439-1-git-send-email-stefan.wahren@i2se.com>
Stefan Wahren <stefan.wahren@i2se.com> writes:
> The main focus of the patch series is to provide support for the new
> Raspberry Pi 3 B+ . The rest are parts which missed the merge window for 4.17.
I've merged this series to my -next branches, and once some kbuilds come
back clean, I'll send PRs up.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180423/39c557ba/attachment.sig>
prev parent reply other threads:[~2018-04-24 1:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 11:28 [PATCH V2 0/9] ARM: bcm283x: RPi 3 B+ support and other improvements Stefan Wahren
2018-04-21 11:28 ` [PATCH V2 1/9] ARM: dts: bcm283x: Fix PWM pin assignment Stefan Wahren
2018-04-21 11:28 ` [PATCH V2 2/9] ARM: dts: bcm2837: Add missing GPIOs of Expander Stefan Wahren
2018-04-21 11:28 ` [PATCH V2 3/9] dt-bindings: bcm: Add Raspberry Pi 3 B+ Stefan Wahren
2018-04-21 11:28 ` [PATCH V2 4/9] ARM: dts: bcm2837: " Stefan Wahren
2018-04-21 11:28 ` [PATCH V2 5/9] ARM: bcm2835_defconfig: Enable LAN78XX driver Stefan Wahren
2018-04-21 11:28 ` [PATCH V2 6/9] ARM: bcm2835_defconfig: Enable VCHIQ driver Stefan Wahren
2018-04-21 11:28 ` [PATCH V2 7/9] ARM: multi_v7_defconfig: Enable LAN and BT for RPi 3 B+ Stefan Wahren
2018-04-21 11:28 ` [PATCH V2 8/9] arm64: defconfig: Enable LAN and BT support " Stefan Wahren
2018-04-21 11:28 ` [PATCH V2 9/9] arm64: dts: broadcom: Add reference to Raspberry Pi " Stefan Wahren
2018-04-24 1:02 ` Eric Anholt [this message]
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=87zi1to1qu.fsf@anholt.net \
--to=eric@anholt.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).