[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190902094802.GT2680@smile.fi.intel.com>
Date: Mon, 2 Sep 2019 12:48:02 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Sakari Ailus <sakari.ailus@...ux.intel.com>
Cc: Petr Mladek <pmladek@...e.com>, linux-kernel@...r.kernel.org,
rafael@...nel.org, linux-acpi@...r.kernel.org,
devicetree@...r.kernel.org, Rob Herring <robh@...nel.org>
Subject: Re: [PATCH v3 07/10] lib/vsprintf: Make use of fwnode API to obtain
node names and separators
On Mon, Sep 02, 2019 at 10:11:30AM +0300, Sakari Ailus wrote:
> On Fri, Aug 30, 2019 at 03:53:14PM +0300, Andy Shevchenko wrote:
> > On Thu, Aug 29, 2019 at 01:10:40PM +0300, Sakari Ailus wrote:
> > > Instead of implementing our own means of discovering parent nodes, node
> > > names or counting how many parents a node has, use the newly added
> > > functions in the fwnode API to obtain that information.
> > >
> >
> > Some style comments below.
> > Nevertheless,
> > Reviewed-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
>
> Thanks!
> > > case 'f': /* full_name */
> > > - buf = device_node_gen_full_name(dn, buf, end);
> >
> > > + buf = fwnode_full_name_string(of_fwnode_handle(dn), buf,
> > > + end);
> >
> > Ditto, disregard checkpatch.
>
> Why? I see no reason to avoid wrapping here; in fact, if I'd review a patch
> that contained such code, I'd ask the submitter to wrap the lines.
For sake of readability. If you look to that file we broke that rule few times
for the same reason.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists