From: Shawn Guo <shawnguo@kernel.org>
To: Stephen Boyd <sboyd@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 fixes for 5.6, round 2
Date: Mon, 16 Mar 2020 08:22:40 +0800 [thread overview]
Message-ID: <20200316002239.GK29269@dragon> (raw)
In-Reply-To: <158352907905.174340.14348638942004736998@swboyd.mtv.corp.google.com>
On Fri, Mar 06, 2020 at 01:11:19PM -0800, Stephen Boyd wrote:
> Quoting Shawn Guo (2020-02-24 04:13:23)
> > The following changes since commit 5eb40257047fb11085d582b7b9ccd0bffe900726:
> >
> > clk: imx8mn: Fix incorrect clock defines (2020-02-17 15:18:00 +0800)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-clk-fixes-5.6-2
> >
> > for you to fetch changes up to 6fb9006abe37e44afaed4f2a5fd3a247a815bb8d:
> >
> > clk: imx8mp: Correct the enet_qos parent clock (2020-02-24 15:38:03 +0800)
> >
> > ----------------------------------------------------------------
> > i.MX clock fixes for 5.6, round 2:
> >
> > - A couple of fixes on i.MX8MP clock driver to correct HDMI_AXI and
> > ENET_QOS_ROOT parent clock.
> > - A couple of fixes on clk-scu driver to ensure that messages sent to
> > i.MX System Controller are 4 bytes aligned.
> >
> > ----------------------------------------------------------------
> > Anson Huang (1):
> > clk: imx8mp: Correct IMX8MP_CLK_HDMI_AXI clock parent
> >
> > Fugang Duan (1):
> > clk: imx8mp: Correct the enet_qos parent clock
> >
> > Leonard Crestez (2):
> > clk: imx: Align imx sc clock msg structs to 4
> > clk: imx: Align imx sc clock parent msg structs to 4
>
> Can you resend without these last two? I don't know what's going on with
> that thread.
Done. Please consider to pull, thanks!
The following changes since commit 5eb40257047fb11085d582b7b9ccd0bffe900726:
clk: imx8mn: Fix incorrect clock defines (2020-02-17 15:18:00 +0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-clk-fixes-5.6-2
for you to fetch changes up to 857c9d31f59f0c0e6117518452ca54883e47d859:
clk: imx8mp: Correct the enet_qos parent clock (2020-03-16 08:18:20 +0800)
----------------------------------------------------------------
i.MX clock fixes for 5.6, round 2:
- A couple of fixes on i.MX8MP clock driver to correct HDMI_AXI and
ENET_QOS_ROOT parent clock.
----------------------------------------------------------------
Anson Huang (1):
clk: imx8mp: Correct IMX8MP_CLK_HDMI_AXI clock parent
Fugang Duan (1):
clk: imx8mp: Correct the enet_qos parent clock
drivers/clk/imx/clk-imx8mp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-16 0:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 12:13 [GIT PULL] i.MX clock fixes for 5.6, round 2 Shawn Guo
2020-03-06 21:11 ` Stephen Boyd
2020-03-16 0:22 ` Shawn Guo [this message]
2020-03-16 18:27 ` 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=20200316002239.GK29269@dragon \
--to=shawnguo@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=sboyd@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).