linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Zong Li <zong.li@sifive.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	linux-clk <linux-clk@vger.kernel.org>,
	linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v3 RESEND] clk: sifive: Fix W=1 kernel build warning
Date: Tue, 11 Jan 2022 09:32:44 +0000	[thread overview]
Message-ID: <Yd1OvFZ4pKw+aTgv@google.com> (raw)
In-Reply-To: <CANXhq0ookagQTZZrNduP5DjXs2awQdRkUxNzTWU=-dz+TVuUwg@mail.gmail.com>

On Tue, 11 Jan 2022, Zong Li wrote:

> On Mon, Jan 10, 2022 at 5:50 PM Lee Jones <lee.jones@linaro.org> wrote:
> >
> > Please improve the subject line.
> >
> > If this is a straight revert, the subject line should reflect that.
> >
> > If not, you need to give us specific information regarding the purpose
> > of this patch.  Please read the Git log for better, more forthcoming
> > examples.
> >
> 
> It seems to me that this patch is not a straight revert, it provides
> another way to fix the original build warnings, just like
> '487dc7bb6a0c' tried to do. I guess the commit message has described
> what the original warnings is and what the root cause is, it also
> mentioned what is changed in this patch. I'm a bit confused whether we
> need to add fixes tag, it looks like that it might cause some
> misunderstanding?

I think it's the patch description and subject that is causing the
misunderstanding.

Please help me with a couple of points and I'll help you draft
something up.

Firstly, what alerted you to the problem you're attempting to solve?

> > > --- a/drivers/clk/sifive/fu540-prci.c
> > > +++ b/drivers/clk/sifive/fu540-prci.c
> > > @@ -20,7 +20,6 @@
> > >
> > >  #include <dt-bindings/clock/sifive-fu540-prci.h>
> > >
> > > -#include "fu540-prci.h"

How is this related to the issue/patch?

> > > +struct prci_clk_desc prci_clk_fu540 = {
> > > +     .clks = __prci_init_clocks_fu540,
> > > +     .num_clks = ARRAY_SIZE(__prci_init_clocks_fu540),
> > > +};

> > > diff --git a/drivers/clk/sifive/fu540-prci.h b/drivers/clk/sifive/fu540-prci.h
> > > index c220677dc010..931d6cad8c1c 100644
> > > --- a/drivers/clk/sifive/fu540-prci.h
> > > +++ b/drivers/clk/sifive/fu540-prci.h
> > > @@ -7,10 +7,6 @@
> > > +extern struct prci_clk_desc prci_clk_fu540;

> > > diff --git a/drivers/clk/sifive/sifive-prci.c b/drivers/clk/sifive/sifive-prci.c
> > > index 80a288c59e56..916d2fc28b9c 100644
> > > --- a/drivers/clk/sifive/sifive-prci.c
> > > +++ b/drivers/clk/sifive/sifive-prci.c
> > > @@ -12,11 +12,6 @@
> > >  #include "fu540-prci.h"
> > >  #include "fu740-prci.h"
> > >
> > > -static const struct prci_clk_desc prci_clk_fu540 = {
> > > -     .clks = __prci_init_clocks_fu540,
> > > -     .num_clks = ARRAY_SIZE(__prci_init_clocks_fu540),
> > > -};
> > > -

I'm not sure if it's you or I that is missing the point here, but
prci_clk_fu540 is used within *this* file itself:

 static const struct of_device_id sifive_prci_of_match[] = {
         {.compatible = "sifive,fu540-c000-prci", .data = &prci_clk_fu540},
         {.compatible = "sifive,fu740-c000-prci", .data = &prci_clk_fu740},
         {}
 };

So why are you moving it out to somewhere it is *not* used and making
it an extern?  This sounds like the opposite to what you'd want?

-- 
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2022-01-11  9:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07  9:07 [PATCH v3 RESEND] clk: sifive: Fix W=1 kernel build warning Zong Li
2022-01-08  0:45 ` Stephen Boyd
2022-01-10  1:52   ` Zong Li
2022-01-10  9:50 ` Lee Jones
2022-01-11  3:21   ` Zong Li
2022-01-11  9:32     ` Lee Jones [this message]
2022-01-12  2:47       ` Zong Li
2022-01-12  9:09         ` Lee Jones
2022-01-13  6:47           ` Zong Li
2022-01-13 17:21             ` Lee Jones
2022-01-13 17:22               ` Lee Jones
2022-01-13 17:51               ` Jessica Clarke
2022-01-13 18:13                 ` Lee Jones
2022-01-14  9:45                   ` Zong Li
2022-01-14 10:07                     ` Lee Jones
2022-01-14 14:59                       ` Zong Li
2022-01-14 16:34                         ` Lee Jones
2022-01-15  6:19                           ` Zong Li
2022-01-19  9:38                             ` Zong Li

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=Yd1OvFZ4pKw+aTgv@google.com \
    --to=lee.jones@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=sboyd@kernel.org \
    --cc=zong.li@sifive.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).