All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: arnd@arndb.de, Scott Branden <scott.branden@broadcom.com>,
	Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
	khilman@kernel.org, Pramod Kumar <pramod.kumar@broadcom.com>,
	arm@kernel.org, Srinath Mannam <srinath.mannam@broadcom.com>,
	bcm-kernel-feedback-list@broadcom.com,
	Ray Jui <ray.jui@broadcom.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 2/6] Broadcom devicetree-arm64 changes for 5.3
Date: Wed, 19 Jun 2019 06:25:09 -0700	[thread overview]
Message-ID: <20190619132509.ax3ze24jgsypicgv@localhost> (raw)
In-Reply-To: <20190612025028.13118-2-f.fainelli@gmail.com>

On Tue, Jun 11, 2019 at 07:50:24PM -0700, Florian Fainelli wrote:
> The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
> 
>   Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
> 
> are available in the Git repository at:
> 
>   https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.3/devicetree-arm64
> 
> for you to fetch changes up to f8526c2d99ca87ccbc0a3da00555d6d08e25d058:
> 
>   arm64: dts: Stingray: Add NIC i2c device node (2019-05-20 09:31:35 -0700)
> 
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM64-based SoCs Device Tree changes
> for 5.3, please pull the following:
> 
> - Pramod adds the Device Tree nodes for thermal support on Stingray
> 
> - Srinath adds the Device Tree nodes for both XHCI (host) and BDC
>   (device) modes
> 
> - Rayagonda adds the Device Tree node for slave I2C operation when
>   Stingray operates as a SmartNIC

Olof merges this branch to arm/dt. Olof thanks Florian.


:-)

-Olof

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

  reply	other threads:[~2019-06-19 13:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12  2:50 [GIT PULL 1/6] Broadcom devicetree changes for 5.3 Florian Fainelli
2019-06-12  2:50 ` [GIT PULL 2/6] Broadcom devicetree-arm64 " Florian Fainelli
2019-06-19 13:25   ` Olof Johansson [this message]
2019-06-12  2:50 ` [GIT PULL 3/6] Broadcom drivers " Florian Fainelli
2019-06-17 11:53   ` Olof Johansson
2019-06-12  2:50 ` [GIT PULL 4/6] Broadcom maintainers " Florian Fainelli
2019-06-19 16:10   ` Olof Johansson
2019-06-12  2:50 ` [GIT PULL 5/6] Broadcom soc " Florian Fainelli
2019-06-12  2:50 ` [GIT PULL 6/6] Broadcom soc-arm64 " Florian Fainelli
2019-06-17 12:16   ` Olof Johansson
2019-06-19 13:35 ` [GIT PULL 1/6] Broadcom devicetree " Olof Johansson
2019-06-23  2:22   ` Florian Fainelli
2019-06-25 11:17     ` Olof Johansson
2019-06-23  3:29 ` [GIT PULL 1/6 v2] Broadcom devicetree changes for 5.2 Florian Fainelli
2019-06-25 11:16   ` Olof Johansson
2019-06-25 12:56     ` 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=20190619132509.ax3ze24jgsypicgv@localhost \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=pramod.kumar@broadcom.com \
    --cc=ray.jui@broadcom.com \
    --cc=rayagonda.kokatanur@broadcom.com \
    --cc=scott.branden@broadcom.com \
    --cc=srinath.mannam@broadcom.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 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.