From: Lee Jones <lee@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: patchwork-bot+bluetooth@kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
pavel@ucw.cz, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, jacek.anaszewski@gmail.com,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2] dt-bindings: leds: Document Bluetooth and WLAN triggers
Date: Fri, 27 Jan 2023 09:27:04 +0000 [thread overview]
Message-ID: <Y9OY6GBAePQ/Y6R2@google.com> (raw)
In-Reply-To: <CABBYNZ+Na7os7D_C_iV22UhyhobxiETjKkngPWVr14QAph6DfQ@mail.gmail.com>
On Thu, 26 Jan 2023, Luiz Augusto von Dentz wrote:
> Hi Lee,
>
> On Thu, Jan 26, 2023 at 12:00 AM Lee Jones <lee@kernel.org> wrote:
> >
> > On Wed, 25 Jan 2023, Luiz Augusto von Dentz wrote:
> >
> > > Hi Lee,
> > >
> > > On Wed, Jan 25, 2023 at 7:16 AM Lee Jones <lee@kernel.org> wrote:
> > > >
> > > > On Tue, 24 Jan 2023, patchwork-bot+bluetooth@kernel.org wrote:
> > > >
> > > > > Hello:
> > > > >
> > > > > This patch was applied to bluetooth/bluetooth-next.git (master)
> > > > > by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
> > > > >
> > > > > On Sun, 22 Jan 2023 11:47:27 +0100 you wrote:
> > > > > > Add the missing trigger patterns for Bluetooth and WLAN activity, which
> > > > > > are already in active use.
> > > > > >
> > > > > > While at it, move the mmc pattern comment where it belongs, and restore
> > > > > > alphabetical sort order.
> > > > > >
> > > > > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > > > > > Reviewed-by: Rob Herring <robh@kernel.org>
> > > > > >
> > > > > > [...]
> > > > >
> > > > > Here is the summary with links:
> > > > > - [v2] dt-bindings: leds: Document Bluetooth and WLAN triggers
> > > > > https://git.kernel.org/bluetooth/bluetooth-next/c/ef017002b93b
> > > >
> > > > Why are you taking LED patches through the Bluetooth tree?
> > >
> > > I assume there isn't a tree dedicated to dt-bindings/leds
> >
> > % ./scripts/get_maintainer.pl -f Documentation/devicetree/bindings/leds/common.yaml
> > Pavel Machek <pavel@ucw.cz> (maintainer:LED SUBSYSTEM,in file)
> > Lee Jones <lee@kernel.org> (maintainer:LED SUBSYSTEM)
> > Rob Herring <robh+dt@kernel.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
> > Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
> > Jacek Anaszewski <jacek.anaszewski@gmail.com> (in file)
> > linux-leds@vger.kernel.org (open list:LED SUBSYSTEM)
> > devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS)
> > linux-kernel@vger.kernel.org (open list)
>
> Well this doesn't tell us what parts of the dt_bindings have a
> dedicated tree and which doesn't, anyway this doesn't show
> linux-bluetooth so I wonder why people are CCing it.
It is not possible to infer responsibilities from how contributors craft
their submissions. The only reliable way to do that is to check the
MAINTAINERS file.
According to the MAINTAINERS excerpt below [0] if a commit only touches
files contained in; drivers/bluetooth/, include/net/bluetooth/ and/or
net/bluetooth/ AND there are no build-time dependencies or dependents,
they are yours to process how you see fit. However, if commits ALSO touch
files outside of those directories OR do have dependencies or
dependents, you will need to consult with the other affected maintainers
to agree on a strategy for merging them. If the aforementioned
directories are not touched (as in this case), you can safely ignore
them - regardless of which mailing list(s) or individual's inboxes they
end up in.
Does that help at all?
[0]
BLUETOOTH DRIVERS
M: Marcel Holtmann <marcel@holtmann.org>
M: Johan Hedberg <johan.hedberg@gmail.com>
M: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
L: linux-bluetooth@vger.kernel.org
S: Supported
W: http://www.bluez.org/
T: git git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git
T: git git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.g
F: drivers/bluetooth/
BLUETOOTH SUBSYSTEM
M: Marcel Holtmann <marcel@holtmann.org>
M: Johan Hedberg <johan.hedberg@gmail.com>
M: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
L: linux-bluetooth@vger.kernel.org
S: Supported
W: http://www.bluez.org/
T: git git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git
T: git git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.g
F: include/net/bluetooth/
F: net/bluetooth/
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-01-27 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 10:47 [PATCH v2] dt-bindings: leds: Document Bluetooth and WLAN triggers Geert Uytterhoeven
2023-01-24 23:40 ` patchwork-bot+bluetooth
2023-01-25 15:12 ` Lee Jones
2023-01-25 19:23 ` Luiz Augusto von Dentz
2023-01-26 8:00 ` Lee Jones
2023-01-26 20:46 ` Luiz Augusto von Dentz
2023-01-27 8:47 ` Krzysztof Kozlowski
2023-01-27 9:27 ` Lee Jones [this message]
2023-01-26 10:01 ` Krzysztof Kozlowski
2023-01-26 8:01 ` Lee Jones
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=Y9OY6GBAePQ/Y6R2@google.com \
--to=lee@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jacek.anaszewski@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=patchwork-bot+bluetooth@kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).