From: Shawn Guo <shawnguo@kernel.org>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: kernel@pengutronix.de, fabio.estevam@nxp.com,
mturquette@baylibre.com, sboyd@codeaurora.org,
aisheng.dong@nxp.com, linux-kernel@vger.kernel.org,
Linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH] clk: imx: imx6sx: update cko mux options
Date: Thu, 22 Feb 2018 11:50:10 +0800 [thread overview]
Message-ID: <20180222035009.GF3217@dragon> (raw)
In-Reply-To: <1516804281-19123-1-git-send-email-Anson.Huang@nxp.com>
On Wed, Jan 24, 2018 at 10:31:21PM +0800, Anson Huang wrote:
> According to latest reference manual (Rev.2, 9/2017),
> previous CKO1/2's mux options are incorrect, update
> them.
>
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
Applied, thanks.
prev parent reply other threads:[~2018-02-22 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 14:31 [PATCH] clk: imx: imx6sx: update cko mux options Anson Huang
2018-02-22 3:50 ` Shawn Guo [this message]
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=20180222035009.GF3217@dragon \
--to=shawnguo@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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