[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VdG6nSHgzmp9yA2aAwvzWuaYf2Q71tz2ruDPnwb=h=hiQ@mail.gmail.com>
Date: Mon, 22 May 2023 12:35:44 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Lee Jones <lee@...nel.org>
Cc: Martin Kurbanov <mmkurbanov@...rdevices.ru>,
Pavel Machek <pavel@....cz>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-kernel@...r.kernel.org, linux-leds@...r.kernel.org,
devicetree@...r.kernel.org, kernel@...rdevices.ru
Subject: Re: [PATCH v4 2/2] leds: add aw20xx driver
On Mon, May 22, 2023 at 10:14 AM Lee Jones <lee@...nel.org> wrote:
> On Thu, 18 May 2023, Andy Shevchenko wrote:
> > On Wed, May 17, 2023 at 10:52 PM Martin Kurbanov
> > <mmkurbanov@...rdevices.ru> wrote:
...
> > I would do
> >
> > i = 0;
> >
> > here and drop the assignment in the definition block to be more robust
>
> "here" where?
> You've removed all context.
That's not true. The below line exclusively defines the location in
the code that I'm talking about. Note, Martin understood that AFAICT
and addressed in the new version.
> > against sudden reuse of i in between.
> >
> > > + device_for_each_child_node(dev, child) {
> >
> > > + i++;
> > > + }
--
With Best Regards,
Andy Shevchenk
Powered by blists - more mailing lists