public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
	arm@kernel.org, linux-imx@nxp.com, kernel@pengutronix.de,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 6/7] Freescale arm64 device tree update for 4.21
Date: Wed, 12 Dec 2018 13:00:53 -0800	[thread overview]
Message-ID: <20181212210053.6bmu5nwxvs5ucyy3@localhost> (raw)
In-Reply-To: <20181210074638.27873-6-shawnguo@kernel.org>

On Mon, Dec 10, 2018 at 03:46:37PM +0800, Shawn Guo wrote:
> 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://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-dt64-4.21
> 
> for you to fetch changes up to 58f5fa68372505c8c6e57754a370f0e7e6004513:
> 
>   arm64: dts: ls1046a: add qdma device tree nodes (2018-12-08 10:28:39 +0800)
> 
> ----------------------------------------------------------------
> Freescale arm64 device tree update for 4.21:
>  - Add device tree for LS1028A SoC and NXP FRWY & QDS boards support
>    based on this SoC.
>  - Add device tree for LX2160A SoC and NXP QDS & RDB boards support
>    based on this SoC.
>  - Add qdma devices for LS1043A and LS1046A SoC.
>  - Disable PCIe device by default in SoC device tree and let board level
>    device tree to enable as needed.
>  - Drop compatible string "snps,dw-pcie" from LayerScape PCIe devices to
>    avoid incorrect matching.
>  - Move fsl-mc device as a child node of soc node, and add missing
>    dma-ranges property for LS1088A SoC.
>  - Update LayerScape SoCs' cooling maps to include all devices affected
>    by individual trip points.

Same comment here about introduction of new SoCs and a brief description, the
patches have a good summary though -- especially LS1028A.

Merged into next/dt now. Thanks!


-Olof


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

  reply	other threads:[~2018-12-12 21:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10  7:46 [GIT PULL 1/7] i.MX drivers changes for 4.21 Shawn Guo
2018-12-10  7:46 ` [GIT PULL 2/7] i.MX SoC " Shawn Guo
2018-12-11  2:51   ` Shawn Guo
2018-12-12 21:53     ` Olof Johansson
2018-12-10  7:46 ` [GIT PULL 3/7] i.MX device tree update " Shawn Guo
2018-12-12 20:55   ` Olof Johansson
2018-12-10  7:46 ` [GIT PULL 4/7] i.MX7D PICO boards " Shawn Guo
2018-12-12 20:56   ` Olof Johansson
2018-12-10  7:46 ` [GIT PULL 5/7] i.MX7ULP device tree " Shawn Guo
2018-12-12 20:58   ` Olof Johansson
2018-12-10  7:46 ` [GIT PULL 6/7] Freescale arm64 device tree update " Shawn Guo
2018-12-12 21:00   ` Olof Johansson [this message]
2018-12-10  7:46 ` [GIT PULL 7/7] i.MX defconfig " Shawn Guo
2018-12-12 21:47   ` Olof Johansson
2018-12-12 21:33 ` [GIT PULL 1/7] i.MX drivers changes " 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=20181212210053.6bmu5nwxvs5ucyy3@localhost \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=shawnguo@kernel.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