From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/3] Broadcom devicetree-arm64 changes for 4.20
Date: Sun, 23 Sep 2018 06:28:34 -0700 [thread overview]
Message-ID: <20180923132834.py7mhe2ikjwjnoje@localhost> (raw)
In-Reply-To: <20180914235928.20551-3-f.fainelli@gmail.com>
On Fri, Sep 14, 2018 at 04:59:28PM -0700, Florian Fainelli wrote:
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
> Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are available in the Git repository at:
>
> https://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.20/devicetree-arm64
>
> for you to fetch changes up to 7cdbe45da1a189e744e6801aebb462ee47235580:
>
> arm64: dts: broadcom: Fix I2C and SPI bus warnings (2018-09-13 15:05:47 -0700)
>
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM64-based SoCs Device Tree changes
> for 4.20, please pull the following:
>
> - Stefan provides a reference to the Compute Module IO Board V3 such
> that we can reference the arm counterpart and still build it for arm64
>
> - Rob fixes I2C and SPI bus warnings which are going to show up with his
> update to DTC scheduled for 4.20
Merged, thanks!
-Olof
next prev parent reply other threads:[~2018-09-23 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 23:59 [GIT PULL 1/3] Broadcom defconfig changes for 4.20 Florian Fainelli
2018-09-14 23:59 ` [GIT PULL 2/3] Broadcom devicetree " Florian Fainelli
2018-09-23 13:28 ` Olof Johansson
2018-09-14 23:59 ` [GIT PULL 3/3] Broadcom devicetree-arm64 " Florian Fainelli
2018-09-23 13:28 ` Olof Johansson [this message]
2018-09-25 18:30 ` [GIT PULL 1/3] Broadcom defconfig " Olof Johansson
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=20180923132834.py7mhe2ikjwjnoje@localhost \
--to=olof@lixom.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).