public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Jiri Slaby <jslaby@suse.cz>, mturquette@baylibre.com
Cc: mliska@suse.cz, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>,
	linux-clk@vger.kernel.org
Subject: Re: [PATCH 1/2] clk: pistachio: Fix initconst confusion
Date: Mon, 11 Jul 2022 13:53:09 -0700	[thread overview]
Message-ID: <20220711205310.EAFFDC34115@smtp.kernel.org> (raw)
In-Reply-To: <98363f27-e7a4-7351-fad7-361f7e465b7e@suse.cz>

Quoting Jiri Slaby (2022-07-08 00:16:12)
> On 29. 06. 22, 10:21, Stephen Boyd wrote:
> > Quoting Jiri Slaby (2022-06-27 00:46:15)
> >> On 24. 06. 22, 2:42, Stephen Boyd wrote:
> >>> Quoting Jiri Slaby (2022-06-23 01:32:16)
> >>>> From: Andi Kleen <ak@linux.intel.com>
> >>>>
> >>>> A variable pointing to const isn't const itself. It'd have to contain
> >>>> "const" keyword after "*" too. Therefore, PNAME() cannot put the strings
> >>>> to "rodata".  Hence use __initdata instead of __initconst to fix this.
> >>>>
> >>>> [js] more explanatory commit message.
> >>>>
> >>>> Cc: Michael Turquette <mturquette@baylibre.com>
> >>>> Cc: Stephen Boyd <sboyd@kernel.org>
> >>>> Cc: linux-clk@vger.kernel.org
> >>>> Signed-off-by: Andi Kleen <ak@linux.intel.com>
> >>>> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> >>>> ---
> >>>>    drivers/clk/pistachio/clk.h | 2 +-
> >>>>    1 file changed, 1 insertion(+), 1 deletion(-)
> >>>>
> >>>> diff --git a/drivers/clk/pistachio/clk.h b/drivers/clk/pistachio/clk.h
> >>>> index f9c31e3a0e47..742e5fab00c0 100644
> >>>> --- a/drivers/clk/pistachio/clk.h
> >>>> +++ b/drivers/clk/pistachio/clk.h
> >>>> @@ -34,7 +34,7 @@ struct pistachio_mux {
> >>>>           const char **parents;
> >>>>    };
> >>>>    
> >>>> -#define PNAME(x) static const char *x[] __initconst
> >>>> +#define PNAME(x) static const char *x[] __initdata
> >>>
> >>> Can it be const char * const and left as __initconst?
> >>
> >> Let me check, IIRC the struct where this is assigned would need to be
> >> updated too.
> >>
> >> I will get into it only some time next week.
> >>
> > 
> > Ok, sounds good. This seems to at least compile locally.
> 
> Yeah, that works. I've sent a v2.
> 
> BTW is the code intended to put the actual strings to .init.rodata? As 
> that was never the case. Only those PNAME defined arrays (pointers to 
> strings) end up in .init.rodata now and the strings are in .rodata.

I think both the strings and the array should be in .init.rodata. The
clk framework deep copies data like parent names.

      reply	other threads:[~2022-07-11 20:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  8:32 [PATCH 1/2] clk: pistachio: Fix initconst confusion Jiri Slaby
2022-06-23  8:32 ` [PATCH 2/2] clk: renesas: rcar-gen4: Fix initconst confusion for cpg_pll_config Jiri Slaby
2022-06-24  0:42   ` Stephen Boyd
2022-06-28 10:03   ` Geert Uytterhoeven
2022-06-24  0:42 ` [PATCH 1/2] clk: pistachio: Fix initconst confusion Stephen Boyd
2022-06-27  7:46   ` Jiri Slaby
2022-06-29  8:21     ` Stephen Boyd
2022-07-08  7:16       ` Jiri Slaby
2022-07-11 20:53         ` Stephen Boyd [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=20220711205310.EAFFDC34115@smtp.kernel.org \
    --to=sboyd@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=jslaby@suse.cz \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mliska@suse.cz \
    --cc=mturquette@baylibre.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