From: Marek Behun <marek.behun@nic.cz>
To: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Cc: Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
Rob Herring <robh+dt@kernel.org>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] MAINTAINERS: add include/dt-bindings/leds/ to linux-leds list
Date: Sat, 26 Sep 2020 19:23:38 +0200 [thread overview]
Message-ID: <20200926192338.0b233f26@nic.cz> (raw)
In-Reply-To: <20200926164745.3779-1-freifunk@adrianschmutzler.de>
On Sat, 26 Sep 2020 18:47:45 +0200
Adrian Schmutzler <freifunk@adrianschmutzler.de> wrote:
> The content of include/dt-bindings/leds/, particularly common.h,
> is apparantly maintained by the linux-leds list. This is also
> explicitly stated in the Documentation.
>
> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 190c7fa2ea01..415f0e089bbe 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9809,6 +9809,7 @@ S: Maintained
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git
> F: Documentation/devicetree/bindings/leds/
> F: drivers/leds/
> +F: include/dt-bindings/leds/
> F: include/linux/leds.h
>
> LEGACY EEPROM DRIVER
Some subsystem maintainers do not want to touch the MAINTAINERS file
because of potential conflict. If Pavel refuses to do this, I was told
that the best way is to send such to Andrew Morton
<akpm@linux-foundation.org>.
Marek
next prev parent reply other threads:[~2020-09-26 17:23 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 [this message]
2020-09-26 19:48 ` Pavel Machek
2020-09-26 20:07 ` Adrian Schmutzler
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=20200926192338.0b233f26@nic.cz \
--to=marek.behun@nic.cz \
--cc=akpm@linux-foundation.org \
--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