Linux LED subsystem development
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: sashiko-bot@kernel.org, sashiko-reviews@lists.linux.dev,
	linux-leds@vger.kernel.org,
	"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: [PATCH v3] leds: is31fl319x: modernize registration
Date: Tue, 11 Aug 2026 19:51:27 +0100	[thread overview]
Message-ID: <20260811185127.GW2869284@google.com> (raw)
In-Reply-To: <20260806135550.2d57682c@kemnade.info>

On Thu, 06 Aug 2026, Andreas Kemnade wrote:

> On Thu, 6 Aug 2026 11:45:25 +0100
> Lee Jones <lee@kernel.org> wrote:
> 
> > On Tue, 04 Aug 2026, Andreas Kemnade wrote:
> > 
> > > On Tue, 04 Aug 2026 13:55:14 +0000
> > > sashiko-bot@kernel.org wrote:
> > >   
> > > > > leds: is31fl319x: modernize registration    
> > > > 
> > > > [Severity: Low]
> > > > This isn't a bug, but should the description after the subsystem prefix be
> > > > capitalized? The LED subsystem guidelines recommend formatting commit messages
> > > > as "leds: <Driver>: <Capitalized description>".  
> > > 
> > > 
> > > ~/linux$ grep -R 'leds: <Driver>: <Capitalized description>"' Documentation/
> > > ~/linux$ ls Documentation/leds/
> > > index.rst                  leds-lp5521.rst      leds-sc27xx.rst
> > > leds-blinkm.rst            leds-lp5523.rst      leds-st1202.rst
> > > leds-cht-wcove.rst         leds-lp5562.rst      ledtrig-oneshot.rst
> > > leds-class-flash.rst       leds-lp55xx.rst      ledtrig-transient.rst
> > > leds-class-multicolor.rst  leds-lp5812.rst      ledtrig-usbport.rst
> > > leds-class.rst             leds-mlxcpld.rst     uleds.rst
> > > leds-el15203000.rst        leds-mt6370-rgb.rst  well-known-leds.txt
> > > leds-lm3556.rst            leds-qcom-lpg.rst
> > > leds-lp3944.rst            leds-s2m-rgb.rst
> > > 
> > > nothing look like special guidelines for the system. I do not want to
> > > see such comments without a reference.
> > > Also MAINTAINERS does not show any additional policy for the LED subsystem.  
> > 
> > `git log --oneline -- <subsystem>` is your friend.
> > 
> That is looking at common practice, not guidelines, which is of course
> often a good idea.
> 
> So Sahiko is hallucinating about non-existant guidelines which
> cannot be referenced of course. Well, at least it gives quite an amount of
> useful hintse.

It's not hallucinating, I put it there. =:-)

https://github.com/sashiko-dev/sashiko/blob/main/third_party/prompts/kernel/subsystem/leds.md

Specifically:

https://github.com/sashiko-dev/sashiko/blob/main/third_party/prompts/kernel/subsystem/leds.md?plain=1#L8

-- 
Lee Jones

      reply	other threads:[~2026-08-11 18:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 13:34 [PATCH v3] leds: is31fl319x: modernize registration Andreas Kemnade
2026-08-04 13:55 ` sashiko-bot
2026-08-04 14:41   ` Andreas Kemnade
2026-08-06 10:45     ` Lee Jones
2026-08-06 11:55       ` Andreas Kemnade
2026-08-11 18:51         ` 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=20260811185127.GW2869284@google.com \
    --to=lee@kernel.org \
    --cc=andreas@kemnade.info \
    --cc=hns@goldelico.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=sashiko-bot@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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