From: Shawn Guo <shawnguo@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Stefan Agner <stefan@agner.ch>, Li Yang <leoyang.li@nxp.com>,
SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 1/7] i.MX drivers update for 5.4
Date: Wed, 11 Sep 2019 09:28:02 +0800 [thread overview]
Message-ID: <20190911012800.GA13923@dragon> (raw)
In-Reply-To: <CAK8P3a17J5aOyKN=q=CLQevUYeRFd0qpE_e5Cz8rSErbrMONyw@mail.gmail.com>
On Tue, Sep 03, 2019 at 10:58:51PM +0200, Arnd Bergmann wrote:
> On Sun, Aug 25, 2019 at 5:33 PM Shawn Guo <shawnguo@kernel.org> wrote:
> >
>
> > i.MX drivers update for 5.4:
> > - A series from Anson Huang to add UID support for i.MX8 SoC and SCU
> > drivers.
> > - A series from Daniel Baluta to add DSP IPC driver for communication
> > between host AP (Linux) and the firmware running on DSP embedded in
> > i.MX8 SoCs.
> > - A small fix for GPCv2 error code printing.
> > - Switch from module_platform_driver_probe() to module_platform_driver()
> > for imx-weim driver, as we need the driver to probe again when device
> > is present later.
> > - Add optional burst clock mode support for imx-weim driver.
>
> Pulled into arm/drivers.
>
> The module_platform_driver_probe() change looks like it should have been
> in a bugfix branch, and I think there were some other patches that would
> qualify in your other pull requests:
>
> a95fbda08ee2 ("ARM: dts: imx7-colibri: disable HS400")
> 9846a4524ac9 ("ARM: dts: imx7d: cl-som-imx7: make ethernet work again")
> 7cb220a75ff3 ("arm64: dts: lx2160a: Fix incorrect I2C clock divider")
> f64697bd0b9e ("arm64: dts: ls1028a: fix gpio nodes")
>
> There may have been good reasons to not include them in the fixes
> pull request, but my feeling is that you could be a little more aggressive
> in categorizing bugfixes for backports or adding Cc:stable tags.
Okay, noted. I was generally relying on author's opinion whether it's a
critical bug fix and should have stable tag.
Shawn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-09-11 1:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 15:32 [GIT PULL 1/7] i.MX drivers update for 5.4 Shawn Guo
2019-08-25 15:32 ` [GIT PULL 2/7] i.MX SoC changes " Shawn Guo
2019-09-03 12:26 ` Arnd Bergmann
2019-08-25 15:32 ` [GIT PULL 3/7] i.MX DT bindings update " Shawn Guo
2019-09-03 14:04 ` Arnd Bergmann
2019-08-25 15:32 ` [GIT PULL 4/7] i.MX device tree update with new clocks Shawn Guo
2019-09-03 14:08 ` Arnd Bergmann
2019-08-25 15:32 ` [GIT PULL 5/7] i.MX arm32 device tree changes for 5.4 Shawn Guo
2019-09-03 14:10 ` Arnd Bergmann
2019-08-25 15:32 ` [GIT PULL 6/7] i.MX arm64 device tree update " Shawn Guo
2019-09-03 14:12 ` Arnd Bergmann
2019-08-25 15:32 ` [GIT PULL 7/7] i.MX defconfig " Shawn Guo
2019-09-03 17:00 ` Arnd Bergmann
2019-09-03 20:58 ` [GIT PULL 1/7] i.MX drivers " Arnd Bergmann
2019-09-11 1:28 ` Shawn Guo [this message]
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=20190911012800.GA13923@dragon \
--to=shawnguo@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--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=soc@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).