From: Sascha Hauer <s.hauer@pengutronix.de>
To: Michael Tretter <m.tretter@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] clk: zynqmp: rename driver specific CLK_MUX_READ_ONLY
Date: Fri, 6 Sep 2019 09:15:18 +0200 [thread overview]
Message-ID: <20190906071518.dhobbezb4b5b4shd@pengutronix.de> (raw)
In-Reply-To: <20190905090606.17748-1-m.tretter@pengutronix.de>
On Thu, Sep 05, 2019 at 11:06:06AM +0200, Michael Tretter wrote:
> Since commit c7cc27d006cc (clk: mux: Support CLK_MUX_READ_ONLY flag)
> Barebox defines the CLK_MUX_READ_ONLY flag like Linux.
>
> The ZynqMP clock driver used the flag before, because this flag is used
> to convey this information from the PMU firmware to the Linux driver.
> However, the flags of the common clock framework and the flag of the
> protocol between PMU firmware and the ZynqMP clock driver should be
> handled separately.
>
> Therefore, add a driver specific prefix to the flag definition in the
> ZynqMP driver.
>
> Fixes the warning
>
> drivers/clk/zynqmp/clk-mux-zynqmp.c:18:0: warning: "CLK_MUX_READ_ONLY" redefined
> In file included from drivers/clk/zynqmp/clk-mux-zynqmp.c:13:0:
> include/linux/clk.h:350:0: note: this is the location of the previous definition
>
> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> ---
> drivers/clk/zynqmp/clk-mux-zynqmp.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-09-06 7:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 9:06 Michael Tretter
2019-09-06 7:15 ` Sascha Hauer [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=20190906071518.dhobbezb4b5b4shd@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.tretter@pengutronix.de \
/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