From: "Adrian Schmutzler" <mail@adrianschmutzler.de>
To: "'Pavel Machek'" <pavel@ucw.cz>,
"'Adrian Schmutzler'" <freifunk@adrianschmutzler.de>
Cc: "'Dan Murphy'" <dmurphy@ti.com>,
"'Rob Herring'" <robh+dt@kernel.org>,
<linux-leds@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: RE: [PATCH] MAINTAINERS: add include/dt-bindings/leds/ to linux-leds list
Date: Sat, 26 Sep 2020 22:07:08 +0200 [thread overview]
Message-ID: <017001d69440$9d873530$d8959f90$@adrianschmutzler.de> (raw)
In-Reply-To: <20200926194809.GA31836@duo.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
> > +F: include/dt-bindings/leds/
> > F: include/linux/leds.h
> I'd not say this is right. I'm not sure what the docs says, but I
> don't commit dt changes without ack from Rob. With yaml stuff, I'm
> even less confident doing so.
> So I'd say Rob maintains this.
https://www.kernel.org/doc/Documentation/leds/leds-class.rst:
"
[...]
If required color or function is missing, please submit a patch
to linux-leds@vger.kernel.org.
[...]
"
This was the only thing pointing me to the linux-leds list when I submitted my patches for LED_FUNCTION_RSSI etc. last week.
I only found it when I had already submitted to Rob and devicetree@ beforehand. However, all of the discussion actually took place at linux-leds@ after I resent there as well.
I do not care who merges this or whom I should send this to, but I think get_maintainers.sh should point me to the correct list where proposed changes are actually discussed (which happened on the linux-leds list).
Best
Adrian
[-- Attachment #2: openpgp-digital-signature.asc --]
[-- Type: application/pgp-signature, Size: 834 bytes --]
prev parent reply other threads:[~2020-09-26 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 16:47 [PATCH] MAINTAINERS: add include/dt-bindings/leds/ to linux-leds list Adrian Schmutzler
2020-09-26 17:23 ` Marek Behun
2020-09-26 19:48 ` Pavel Machek
2020-09-26 20:07 ` Adrian Schmutzler [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='017001d69440$9d873530$d8959f90$@adrianschmutzler.de' \
--to=mail@adrianschmutzler.de \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=freifunk@adrianschmutzler.de \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@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