From: Olof Johansson <olof@lixom.net>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Stefan Agner <stefan@agner.ch>, Li Yang <leoyang.li@nxp.com>,
arm@kernel.org, linux-imx@nxp.com, kernel@pengutronix.de,
Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/7] i.MX drivers change for 5.3
Date: Tue, 25 Jun 2019 05:45:38 -0700 [thread overview]
Message-ID: <20190625124538.wrxlx6mk3vtyij3m@localhost> (raw)
In-Reply-To: <20190625075305.29082-1-shawnguo@kernel.org>
On Tue, Jun 25, 2019 at 03:52:59PM +0800, Shawn Guo 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:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-drivers-5.3
>
> for you to fetch changes up to db10496c0064ba3355936de801cd3ba0b6711bd1:
>
> soc: imx: Add i.MX8MN SoC driver support (2019-06-24 09:15:57 +0800)
>
> ----------------------------------------------------------------
> i.MX driver changes for 5.3:
> - Add i.MX SCU based SoC bus driver for i.MX8QXP SoC support, which
> talks to SCU firmware for getting SoC ID and revision.
> - Update soc-imx8 bus driver to read imx8mm soc revision from anatop.
> - Add i.MX8MN SoC bus support into soc-imx8 driver.
> - Various small improvements on soc-imx8 bus driver.
>
> ----------------------------------------------------------------
> Anson Huang (6):
> soc: imx: Add SCU SoC info driver support
> soc: imx: soc-imx8: Avoid unnecessary of_node_put() in error handling
> soc: imx: soc-imx8: Correct return value of error handle
> soc: imx8: Fix potential kernel dump in error path
> soc: imx8: Use existing of_root directly
> soc: imx: Add i.MX8MN SoC driver support
Given that these were posted at the same time, it seems silly to post a patch
with a fix right after -- they should probably be squashed before sending out
(or when applying).
Anyway, minor nit. Merged the branch.
Thanks!
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-25 13:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 7:52 [GIT PULL 1/7] i.MX drivers change for 5.3 Shawn Guo
2019-06-25 7:53 ` [GIT PULL 2/7] i.MX SoC changes " Shawn Guo
2019-06-25 12:52 ` Olof Johansson
2019-06-25 7:53 ` [GIT PULL 3/7] i.MX DT bindings update " Shawn Guo
2019-06-25 11:51 ` Olof Johansson
2019-06-25 7:53 ` [GIT PULL 4/7] i.MX DT changes with new clock " Shawn Guo
2019-06-25 11:52 ` Olof Johansson
2019-06-25 7:53 ` [GIT PULL 5/7] i.MX arm32 DT changes " Shawn Guo
2019-06-25 11:52 ` Olof Johansson
2019-06-25 7:53 ` [GIT PULL 6/7] i.MX arm64 " Shawn Guo
2019-06-25 11:53 ` Olof Johansson
2019-06-25 7:53 ` [GIT PULL 7/7] i.MX defconfig " Shawn Guo
2019-06-25 12:32 ` Olof Johansson
2019-06-26 2:02 ` Shawn Guo
2019-06-27 2:14 ` Olof Johansson
2019-06-27 13:25 ` Shawn Guo
2019-06-25 12:45 ` Olof Johansson [this message]
2019-06-26 1:48 ` [GIT PULL 1/7] i.MX drivers change " Shawn Guo
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=20190625124538.wrxlx6mk3vtyij3m@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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).