From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/6] i.MX drivers updates for 4.17
Date: Fri, 16 Mar 2018 08:47:20 +0800 [thread overview]
Message-ID: <20180316004719.GL26859@dragon> (raw)
In-Reply-To: <CAK8P3a32SL4vaD+o8wRWDnnv0e0k5qyER9Ly-2j9PZAOrkyV6w@mail.gmail.com>
On Thu, Mar 15, 2018 at 04:25:10PM +0100, Arnd Bergmann wrote:
> On Thu, Mar 15, 2018 at 12:36 PM, Shawn Guo <shawnguo@kernel.org> wrote:
> > The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
> >
> > Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-drivers-4.17
> >
> > for you to fetch changes up to f40a1e3705be23e845fbeec66acf3a6582524145:
> >
> > soc: imx: gpc: ARM power domain should be always-on (2018-02-12 13:07:48 +0800)
> >
> > ----------------------------------------------------------------
> > i.MX drivers update for 4.17:
> > - Set GENPD_FLAG_ALWAYS_ON flag for ARM power domain to avoid incorrect
> > power state in sysfs pm_genpd_summary output.
>
> Pulled into next/drivers. I can't really tell from the patch description whether
> this is urgent or not. Can you confirm that we don't want this in 4.16 or older
> kernels?
My understanding is that it's not so urgent or critical for older
kernels. @Anson, let us know if you think differently.
Shawn
next prev parent reply other threads:[~2018-03-16 0:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 11:36 [GIT PULL 1/6] i.MX drivers updates for 4.17 Shawn Guo
2018-03-15 11:36 ` [GIT PULL 2/6] i.MX SoC changes " Shawn Guo
2018-03-15 15:12 ` Arnd Bergmann
2018-03-16 0:55 ` Shawn Guo
2018-03-15 11:36 ` [GIT PULL 3/6] i.MX device tree updates with new clock " Shawn Guo
2018-03-15 15:03 ` Arnd Bergmann
2018-03-15 11:36 ` [GIT PULL 4/6] i.MX device tree updates " Shawn Guo
2018-03-15 15:08 ` Arnd Bergmann
2018-03-15 16:58 ` Arnd Bergmann
2018-03-15 17:22 ` Fabio Estevam
2018-03-15 18:12 ` Fabio Estevam
2018-03-16 1:30 ` Shawn Guo
2018-03-15 11:36 ` [GIT PULL 5/6] Freescale arm64 " Shawn Guo
2018-03-15 15:29 ` Arnd Bergmann
2018-03-16 1:56 ` Shawn Guo
2018-03-15 11:36 ` [GIT PULL 6/6] i.MX defconfig " Shawn Guo
2018-03-15 15:21 ` Arnd Bergmann
2018-03-15 22:48 ` Fabio Estevam
2018-03-15 23:06 ` Fabio Estevam
2018-03-26 11:42 ` [GIT PULL v2 " Shawn Guo
2018-03-27 13:11 ` Arnd Bergmann
2018-03-15 15:25 ` [GIT PULL 1/6] i.MX drivers " Arnd Bergmann
2018-03-16 0:47 ` Shawn Guo [this message]
2018-03-16 1:22 ` Anson Huang
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=20180316004719.GL26859@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).