All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Shawn Guo <shawnguo@kernel.org>
Cc: linux-clk@vger.kernel.org, kernel@pengutronix.de,
	Fabio Estevam <festevam@gmail.com>,
	Stefan Agner <stefan@agner.ch>,
	linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] i.MX clock changes for 5.4
Date: Wed, 04 Sep 2019 11:13:10 -0700	[thread overview]
Message-ID: <20190904181311.BFD1F208E4@mail.kernel.org> (raw)
In-Reply-To: <20190825115505.GA20454@X250>

Quoting Shawn Guo (2019-08-25 04:55:06)
> Hi Stephen,
> 
> This is the i.MX clock changes I collected for 5.4.  Please help pull,
> and keep commit 6ad7cb7122ce ("clk: imx8: Add DSP related clocks")
> stable, as I pulled it into my DT branch as dependency.  Thanks!
> 
> Shawn
> 
> 
> The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
> 
>   Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/clk-imx-5.4
> 
> for you to fetch changes up to 760e548e7f885d89bf2dfab4838df9379edd19fc:
> 
>   clk: imx: imx8mn: fix audio pll setting (2019-08-24 21:04:27 +0200)
> 
> ----------------------------------------------------------------

Thanks. Pulled into clk-next


WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Stefan Agner <stefan@agner.ch>,
	linux-imx@nxp.com, kernel@pengutronix.de,
	Fabio Estevam <festevam@gmail.com>,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] i.MX clock changes for 5.4
Date: Wed, 04 Sep 2019 11:13:10 -0700	[thread overview]
Message-ID: <20190904181311.BFD1F208E4@mail.kernel.org> (raw)
In-Reply-To: <20190825115505.GA20454@X250>

Quoting Shawn Guo (2019-08-25 04:55:06)
> Hi Stephen,
> 
> This is the i.MX clock changes I collected for 5.4.  Please help pull,
> and keep commit 6ad7cb7122ce ("clk: imx8: Add DSP related clocks")
> stable, as I pulled it into my DT branch as dependency.  Thanks!
> 
> Shawn
> 
> 
> The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
> 
>   Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/clk-imx-5.4
> 
> for you to fetch changes up to 760e548e7f885d89bf2dfab4838df9379edd19fc:
> 
>   clk: imx: imx8mn: fix audio pll setting (2019-08-24 21:04:27 +0200)
> 
> ----------------------------------------------------------------

Thanks. Pulled into clk-next


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

  reply	other threads:[~2019-09-04 18:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-25 11:55 [GIT PULL] i.MX clock changes for 5.4 Shawn Guo
2019-08-25 11:55 ` Shawn Guo
2019-09-04 18:13 ` Stephen Boyd [this message]
2019-09-04 18:13   ` Stephen Boyd

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=20190904181311.BFD1F208E4@mail.kernel.org \
    --to=sboyd@kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.