Devicetree
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: "Flávio Amieiro" <flavio@amieiro.net>
Cc: Pavel Machek <pavel@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/2] leds: is31f132xx: Add support for is31fl3206
Date: Wed, 28 Oct 2026 15:13:41 +0000	[thread overview]
Message-ID: <20261028151341.GE3605912@google.com> (raw)
In-Reply-To: <87bj8noj35.fsf@berlin>

On Tue, 20 Oct 2026, Flávio Amieiro wrote:

> Lee Jones <lee@kernel.org> writes:
> 
> > --- checkpatch.pl (1 issue) ---
> > Line 172: WARNING: DT compatible string "issi,is31fl3206" appears un-documented -- check ./Documentation/devicetree/bindings/
> >
> > This true, or is it documented in this set?
> >
> 
> It is documented in the first patch in the series[1].
> 
> 
> >
> > New for() loops should initiate the variable.
> >
> >   for (int i = 0; ...
> >
> 
> I will make sure to initialize the variable in the loop for any new code
> I add in v4. Some of this code, though, was old code that simply moved
> around (and by changing the approach in v4 it might not move anymore).
> 
> Should I add a patch to the series to fix this in portions of the code I
> move to another place?
> 
> If it is helpful, I can also change this in the entire file, just let me
> know if this is welcome as a patch in this series or if it better to
> send it in a different one.
> 
> >
> > Spaces around '+' please.
> >
> 
> This is the same as the for loops: I'll make sure to take this into
> consideration for code added in v4.
> 
> >
> > I detest pointers to functions at the device driver level.
> >
> > Please find another way to do this.
> >
> 
> I'll find another approach for this but, since this is my first patch,
> maybe it's better to align on it before sending in a new version
> unnecessarily to the list.

Sorry, I don't have the time to learn about your device.

Have a think about other ways you can support what you're trying to do,
then attempt to find a solid precedent for it.  You can submit
subsequent attempts "unnecessarily", no one is going to get mad.

-- 
Lee Jones

      reply	other threads:[~2026-10-28 15:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 10:00 [PATCH v3 0/2] leds: Add support for the is31fl3206 LED driver Flavio Amieiro
2026-10-13 10:00 ` [PATCH v3 1/2] dt-bindings: leds: Add issi,is31fl3206 to leds-is31fl32xx Flavio Amieiro
2026-10-13 10:00 ` [PATCH v3 2/2] leds: is31f132xx: Add support for is31fl3206 Flavio Amieiro
2026-10-20 11:03   ` Lee Jones
2026-10-21  2:58     ` Flávio Amieiro
2026-10-28 15:13       ` Lee Jones [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=20261028151341.GE3605912@google.com \
    --to=lee@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=flavio@amieiro.net \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@kernel.org \
    --cc=robh@kernel.org \
    /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