Resending as plain text because the mailing lists rejected the previous HTML copy.
You are right, I should have explained this explicitly. I dropped your Reviewed-by because v5 materially changed the binding: it adds the dash-suffixed multicolor-group form, makes reg optional for that form so groups can begin at outputs 16 or 17, and documents the RISET/current-limit relationship. I did not intend to ask you to repeat the review without explaining why. I will record this explicitly in the next revision and will not carry the tag unless you renew it. Sorry for the omission. On Sun, Aug 16, 2026 at 11:42 PM Krzysztof Kozlowski <[email protected]> wrote: > > On Fri, Aug 14, 2026 at 04:10:49PM -0700, Ahmad Byagowi wrote: > > The IS32FL3207 is an 18-channel constant-current LED controller with > > per-output PWM and current scaling. > > > > Describe I2C addressing, power and shutdown controls, RISET, and > > individual or multicolor output groupings. Require board current limits > > for each output and document their relationship to the RISET-derived full > > scale. > > > > Allow dash-suffixed multicolor group names when a group begins at channel > > 16 or 17, which cannot be represented by the common schema unit-address > > form. > > > > Signed-off-by: Ahmad Byagowi <[email protected]> > > --- > > .../bindings/leds/issi,is32fl3207.yaml | 281 ++++++++++++++++++ > > I do not see any explanation why you dropped review. > > We have enough of other patches to review, so if you ask us to do the > same work twice, it's only fair if we just skip your patches. > > <form letter> > This is a friendly reminder during the review process. > > It looks like you received a tag and forgot to add it. > > If you do not know the process, here is a short explanation: > Please add Acked-by/Reviewed-by/Tested-by tags when posting new > versions of patchset, under or above your Signed-off-by tag, unless > patch changed significantly (e.g. new properties added to the DT > bindings). Tag is "received", when provided in a message replied to you > on the mailing list. Tools like b4 can help here. However, there's no > need to repost patches *only* to add the tags. The upstream maintainer > will do that for tags received on the version they apply. > > Please read: > https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577 > > If a tag was not added on purpose, please state in the patch changelog > or cover letter why and what changed. > </form letter> > > Best regards, > Krzysztof > -- 73 With best wishes / Mit herzlichsten Grüßen Ahmad Byagowi, Ph.D., Dr. Techn., P.Eng. Phone: +1 (650) 924 6653 Please consider the environment before printing this e-mail.
