public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	Stefan Agner <stefan@agner.ch>, Li Yang <leoyang.li@nxp.com>,
	Sascha Hauer <kernel@pengutronix.de>,
	NXP Linux Team <linux-imx@nxp.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 1/6] i.MX drivers update for 5.17
Date: Tue, 21 Dec 2021 14:57:08 +0800	[thread overview]
Message-ID: <20211221065708.GB14131@dragon> (raw)
In-Reply-To: <CAK8P3a0Pi+9tNTfaNjKCLH1f3Ge4YLW9_7o1ci1RLeuTOVEbkQ@mail.gmail.com>

On Mon, Dec 20, 2021 at 05:28:04PM +0100, Arnd Bergmann wrote:
> On Sat, Dec 18, 2021 at 8:14 AM Shawn Guo <shawnguo@kernel.org> wrote:
> >
> > The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:
> >
> >   Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)
> >
> > are available in the Git repository at:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-drivers-5.17
> >
> > for you to fetch changes up to 7f511d514e8c34b6dd0c17b5496e48b2a6a2626c:
> >
> >   soc: imx: imx8m-blk-ctrl: add i.MX8MN DISP blk-ctrl (2021-12-17 10:53:20 +0800)
> >
> > ----------------------------------------------------------------
> > i.MX drivers update for 5.17:
> >
> > - A number of patches from Adam Ford to update gpcv2 and blk-ctrl driver
> >   to keep i.MX8MM VPU-H1 and i.MX8MN GPUMIX bus clocks active, and add
> >   i.MX8MN display related domain support.
> > - Add optional continuous burst clock support for imx-weim bus driver.
> > - Call pm_runtime_put_sync_suspend() instead of pm_runtime_put() in
> >   gpcv2 driver to prevent a sequence issue seen with i.MX8MM GPU and
> >   MIX domain.
> 
> Thanks, I've pulled all six tags now, but I don't know why there are no
> automated emails about them, this seems to happen for some senders
> but not others.

I sent the PRs in form of patches (manually editing) with 'git
send-email'.  I have been doing this for years, and I used to get
automated emails about merging.  Not sure what's changed recently.

Shawn

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

  reply	other threads:[~2021-12-21  6:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-18  7:14 [GIT PULL 1/6] i.MX drivers update for 5.17 Shawn Guo
2021-12-18  7:14 ` [GIT PULL 2/6] i.MX SoC " Shawn Guo
2021-12-18  7:14 ` [GIT PULL 3/6] i.MX dt-bindings " Shawn Guo
2021-12-18  7:14 ` [GIT PULL 4/6] i.MX arm device tree change " Shawn Guo
2021-12-18  7:14 ` [GIT PULL 5/6] i.MX arm64 " Shawn Guo
2021-12-18  7:14 ` [GIT PULL 6/6] i.MX defconfig update " Shawn Guo
2021-12-20 16:28 ` [GIT PULL 1/6] i.MX drivers " Arnd Bergmann
2021-12-21  6:57   ` Shawn Guo [this message]
2021-12-23 15:04     ` Arnd Bergmann

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=20211221065708.GB14131@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