public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Stephen Boyd <sboyd@codeaurora.org>,
	Michael Turquette <mturquette@baylibre.com>
Cc: kernel@pengutronix.de, linux-clk@vger.kernel.org,
	linux-imx@nxp.com, Fabio Estevam <fabio.estevam@nxp.com>
Subject: [GIT PULL] i.MX clock fixes for 4.16
Date: Wed, 28 Feb 2018 08:45:34 +0800	[thread overview]
Message-ID: <20180228004533.GY3217@dragon> (raw)

Hi Stephen, Michael,

Please consider to take this into 4.16 as fix.  There are details about
this pull request in tag description.  Thanks.

Shawn


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/clk-imx-fixes-4.16

for you to fetch changes up to a275b315334dea3c2151094765387ede421aac92:

  clk: imx51-imx53: Fix UART4/5 registration on i.MX50 and i.MX53 (2018-02-22 11:27:30 +0800)

----------------------------------------------------------------
i.MX clock fixes for 4.16:
 - Update i.MX5 clock driver to register UART4/5 clock only on i.MX50
   and i.MX53.  It fixes a kernel warning seen on i.MX53, caused by
   commit 59dc3d8c8673 ("clk: imx51: uart4, uart5 gates only exist on
   imx50, imx53").

----------------------------------------------------------------
Fabio Estevam (1):
      clk: imx51-imx53: Fix UART4/5 registration on i.MX50 and i.MX53

 drivers/clk/imx/clk-imx51-imx53.c | 20 +++++++++++++++++---
 1 file changed, 17 insertions(+), 3 deletions(-)

             reply	other threads:[~2018-02-28  0:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28  0:45 Shawn Guo [this message]
2018-03-10  0:21 ` [GIT PULL] i.MX clock fixes for 4.16 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=20180228004533.GY3217@dragon \
    --to=shawnguo@kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.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