All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Kevin Hilman <khilman@kernel.org>, Eric Anholt <eric@anholt.net>,
	arm-soc <arm@kernel.org>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	Stefan Wahren <wahrenst@gmx.net>, Olof Johansson <olof@lixom.net>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 3/3] Broadcom devicetree changes for 5.4
Date: Wed, 4 Sep 2019 17:12:16 +0200	[thread overview]
Message-ID: <CAK8P3a2QmUsdDeaCiwv2WgL8BNUHn=LOB26Buknk2SUKb=QvgQ@mail.gmail.com> (raw)
In-Reply-To: <20190819190552.11254-3-f.fainelli@gmail.com>

On Mon, Aug 19, 2019 at 9:06 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
> This pull request contains Broadcom ARM-based SoCs Device Tree updates
> for 5.4, please pull the following:
>
> - Stefan does a bunch of preparatory work for supporting the Raspberry
>   Pi 4in the next merge window correct register ranges (SPI, I2C,
>   UART), define memory, HDMI and MMC properties at the board level
>


Pulled into arm/dt, thanks!

      Arnd

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-09-04 15:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 19:05 [GIT PULL 1/3] Broadcom defconfig changes for 5.4 Florian Fainelli
2019-08-19 19:05 ` [GIT PULL 2/3] Broadcom defconfig-arm64 " Florian Fainelli
2019-09-04 13:02   ` Arnd Bergmann
2019-09-04 17:06     ` Stefan Wahren
2019-09-04 20:19       ` Arnd Bergmann
2019-08-19 19:05 ` [GIT PULL 3/3] Broadcom devicetree " Florian Fainelli
2019-09-04 15:12   ` Arnd Bergmann [this message]
2019-09-04 12:59 ` [GIT PULL 1/3] Broadcom defconfig " Arnd Bergmann
2019-09-04 17:07   ` 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='CAK8P3a2QmUsdDeaCiwv2WgL8BNUHn=LOB26Buknk2SUKb=QvgQ@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=arm@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=eric@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=olof@lixom.net \
    --cc=wahrenst@gmx.net \
    /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.