From: Shawn Guo <shawnguo@kernel.org>
To: kbuild test robot <lkp@intel.com>
Cc: Dong Aisheng <aisheng.dong@nxp.com>, Peng Fan <peng.fan@nxp.com>,
kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH shawnguo] clk: imx: imx8m_clk_composite_mux_ops can be static
Date: Thu, 21 May 2020 22:39:11 +0800 [thread overview]
Message-ID: <20200521143910.GA24084@dragon> (raw)
In-Reply-To: <20200521110439.GA55876@f61f8b3f25ca>
On Thu, May 21, 2020 at 07:04:39PM +0800, kbuild test robot wrote:
>
> Fixes: 3f0365dafe32 ("clk: imx: add mux ops for i.MX8M composite clk")
> Signed-off-by: kbuild test robot <lkp@intel.com>
> ---
> clk-composite-8m.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/imx/clk-composite-8m.c b/drivers/clk/imx/clk-composite-8m.c
> index 8fa60f22d377f..2d9562ebddc3f 100644
> --- a/drivers/clk/imx/clk-composite-8m.c
> +++ b/drivers/clk/imx/clk-composite-8m.c
> @@ -164,7 +164,7 @@ imx8m_clk_composite_mux_determine_rate(struct clk_hw *hw,
> }
>
>
> -const struct clk_ops imx8m_clk_composite_mux_ops = {
> +static const struct clk_ops imx8m_clk_composite_mux_ops = {
Amended the change. Thanks!
Shawn
> .get_parent = imx8m_clk_composite_mux_get_parent,
> .set_parent = imx8m_clk_composite_mux_set_parent,
> .determine_rate = imx8m_clk_composite_mux_determine_rate,
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-05-21 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202005211954.Rc03oK6u%lkp@intel.com>
2020-05-21 11:04 ` [RFC PATCH shawnguo] clk: imx: imx8m_clk_composite_mux_ops can be static kbuild test robot
2020-05-21 14:39 ` 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=20200521143910.GA24084@dragon \
--to=shawnguo@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkp@intel.com \
--cc=peng.fan@nxp.com \
/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).