[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfhLDpuJD+ftdEWt3bwooRD5U=KfOnKZeKm9d4N21HOtw@mail.gmail.com>
Date: Thu, 30 Jan 2020 22:43:25 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Suman Anna <s-anna@...com>
Cc: Lee Jones <lee.jones@...aro.org>, Arnd Bergmann <arnd@...db.de>,
David Lechner <david@...hnology.com>,
Tony Lindgren <tony@...mide.com>,
Roger Quadros <rogerq@...com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@...ts.infradead.org>,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>
Subject: Re: [PATCH v2] mfd: syscon: Use a unique name with regmap_config
On Thu, Jan 30, 2020 at 7:09 PM Suman Anna <s-anna@...com> wrote:
> On 1/30/20 9:34 AM, Andy Shevchenko wrote:
> > On Tue, Jan 28, 2020 at 1:14 AM Suman Anna <s-anna@...com> wrote:
...
> >> - syscon_config.name = of_node_full_name(np);
> >> + syscon_config.name = kasprintf(GFP_KERNEL, "%pOFn@...x", np,
> >> + (u64)res.start);
> >
> > Explicit castings in printf() usually tell us that something is not okay.
>
> Yes, I agree in general.
>
> > Yes, for resource_size_t we have %pa.
>
> And that was the first thing I tried when doing v2, before moving away
> from it. This is not for a console printf statement, but is rather for
> the regmap debugfs name. Using a %pa adds the 0x and leading zeros in
> the debugfs name, when compared to the name before this patch. The
> typecast retains the current format, and replaces the unit-address
> without the leading 0s either. Introducing a local-variable to avoid the
> typecast is overkill.
Thanks for the clarification.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists