From: Aisheng Dong <aisheng.dong@nxp.com>
To: Abel Vesa <abel.vesa@nxp.com>,
Sascha Hauer <kernel@pengutronix.de>,
Lucas Stach <l.stach@pengutronix.de>,
Stephen Boyd <sboyd@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
dl-linux-imx <linux-imx@nxp.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Abel Vesa <abelvesa@linux.com>
Subject: RE: [PATCH] clk: imx: Remove Kconfig duplicate include
Date: Fri, 4 Jan 2019 03:22:33 +0000 [thread overview]
Message-ID: <AM0PR04MB4211D60709FC53F8058B043E808E0@AM0PR04MB4211.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1546534688-17842-1-git-send-email-abel.vesa@nxp.com>
> From: Abel Vesa
> Sent: Friday, January 4, 2019 12:58 AM
> Subject: [PATCH] clk: imx: Remove Kconfig duplicate include
>
> Commit d360b130e210f2 ("clk: imx: Make the i.MX8MQ CCM clock driver
> CLK_IMX8MQ dependant") introduced this dupplicate (and wrongfuly
> ordered).
>
> Fixes: d360b130e210f2 ("clk: imx: Make the i.MX8MQ CCM clock driver
> CLK_IMX8MQ dependant")
> Signed-off-by: Abel Vesa <abel.vesa@nxp.com>
Reviewed-by: Dong Aisheng <aisheng.dong@nxp.com>
Regards
Dong Aisheng
> ---
> drivers/clk/Kconfig | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig index e5b2fe8..d2f0bb5
> 100644
> --- a/drivers/clk/Kconfig
> +++ b/drivers/clk/Kconfig
> @@ -293,7 +293,6 @@ config COMMON_CLK_BD718XX source
> "drivers/clk/actions/Kconfig"
> source "drivers/clk/bcm/Kconfig"
> source "drivers/clk/hisilicon/Kconfig"
> -source "drivers/clk/imx/Kconfig"
> source "drivers/clk/imgtec/Kconfig"
> source "drivers/clk/imx/Kconfig"
> source "drivers/clk/ingenic/Kconfig"
> --
> 2.7.4
next prev parent reply other threads:[~2019-01-04 3:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 16:58 [PATCH] clk: imx: Remove Kconfig duplicate include Abel Vesa
2019-01-04 3:22 ` Aisheng Dong [this message]
2019-01-09 18:44 ` 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=AM0PR04MB4211D60709FC53F8058B043E808E0@AM0PR04MB4211.eurprd04.prod.outlook.com \
--to=aisheng.dong@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=abelvesa@linux.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.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;
as well as URLs for NNTP newsgroup(s).