linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Stefan Wahren <stefan.wahren@i2se.com>,
	bcm-kernel-feedback-list@broadcom.com,
	Eric Anholt <eric@anholt.net>
Subject: [GIT PULL 4/4] bcm2835-dt-next-2018-11-27
Date: Tue, 27 Nov 2018 13:13:01 -0800	[thread overview]
Message-ID: <20181127211301.30296-4-eric@anholt.net> (raw)
In-Reply-To: <20181127211301.30296-1-eric@anholt.net>

Hi Florian,

The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:

  Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)

are available in the Git repository at:

  git://github.com/anholt/linux tags/bcm2835-dt-next-2018-11-27

for you to fetch changes up to 703c605fac82d580822dc39f5eff9e2fe66ed63d:

  ARM: dts: bcm2835-rpi-zero: Switch to SPDX identifier (2018-11-13 19:32:28 +0100)

----------------------------------------------------------------
This pull request adds a compatible string to the DT necessary for the
firmware and VCHI driver to coordinate on using the correct cache line
size for the platform.

----------------------------------------------------------------
Phil Elwell (3):
      dt-bindings: soc: Document "brcm,bcm2836-vchiq"
      ARM: dts: bcm283x: Correct vchiq compatible string
      ARM: dts: bcm283x: Correct mailbox register sizes

Stefan Wahren (1):
      ARM: dts: bcm2835-rpi-zero: Switch to SPDX identifier

 Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-vchiq.txt | 3 ++-
 arch/arm/boot/dts/bcm2835-rpi-zero-w.dts                         | 8 +-------
 arch/arm/boot/dts/bcm2835-rpi-zero.dts                           | 8 +-------
 arch/arm/boot/dts/bcm2835-rpi.dtsi                               | 4 ++--
 arch/arm/boot/dts/bcm2836-rpi-2-b.dts                            | 2 +-
 arch/arm/boot/dts/bcm2836-rpi.dtsi                               | 6 ++++++
 arch/arm/boot/dts/bcm2837-rpi-3-b-plus.dts                       | 2 +-
 arch/arm/boot/dts/bcm2837-rpi-3-b.dts                            | 2 +-
 arch/arm/boot/dts/bcm2837-rpi-cm3.dtsi                           | 2 +-
 9 files changed, 16 insertions(+), 21 deletions(-)
 create mode 100644 arch/arm/boot/dts/bcm2836-rpi.dtsi

  parent reply	other threads:[~2018-11-27 21:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 21:12 [GIT PULL 1/4] bcm2835-defconfig-next-2018-11-27 Eric Anholt
2018-11-27 21:12 ` [GIT PULL 2/4] bcm2835-soc-next-2018-11-27 Eric Anholt
2018-11-28 21:48   ` Florian Fainelli
2018-11-27 21:13 ` [GIT PULL 3/4] bcm2835-drivers-next-2018-11-27 Eric Anholt
2018-11-28 21:48   ` Florian Fainelli
2018-11-27 21:13 ` Eric Anholt [this message]
2018-11-28 21:49   ` [GIT PULL 4/4] bcm2835-dt-next-2018-11-27 Florian Fainelli
2018-11-28 21:48 ` [GIT PULL 1/4] bcm2835-defconfig-next-2018-11-27 Florian Fainelli
2019-01-09 18:38   ` Stefan Wahren
2019-01-14 18:36     ` 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=20181127211301.30296-4-eric@anholt.net \
    --to=eric@anholt.net \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=stefan.wahren@i2se.com \
    /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).