On Thu, 26 Jan 2023, Luiz Augusto von Dentz wrote: > Hi Lee, > > On Thu, Jan 26, 2023 at 12:00 AM Lee Jones <lee@xxxxxxxxxx> 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@xxxxxxxxxx> wrote: > > > > > > > > On Tue, 24 Jan 2023, patchwork-bot+bluetooth@xxxxxxxxxx wrote: > > > > > > > > > Hello: > > > > > > > > > > This patch was applied to bluetooth/bluetooth-next.git (master) > > > > > by Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx>: > > > > > > > > > > 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@xxxxxxxxx> > > > > > > Reviewed-by: Rob Herring <robh@xxxxxxxxxx> > > > > > > > > > > > > [...] > > > > > > > > > > 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@xxxxxx> (maintainer:LED SUBSYSTEM,in file) > > Lee Jones <lee@xxxxxxxxxx> (maintainer:LED SUBSYSTEM) > > Rob Herring <robh+dt@xxxxxxxxxx> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) > > Krzysztof Kozlowski <krzysztof.kozlowski+dt@xxxxxxxxxx> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) > > Jacek Anaszewski <jacek.anaszewski@xxxxxxxxx> (in file) > > linux-leds@xxxxxxxxxxxxxxx (open list:LED SUBSYSTEM) > > devicetree@xxxxxxxxxxxxxxx (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) > > linux-kernel@xxxxxxxxxxxxxxx (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@xxxxxxxxxxxx> M: Johan Hedberg <johan.hedberg@xxxxxxxxx> M: Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> L: linux-bluetooth@xxxxxxxxxxxxxxx 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@xxxxxxxxxxxx> M: Johan Hedberg <johan.hedberg@xxxxxxxxx> M: Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> L: linux-bluetooth@xxxxxxxxxxxxxxx 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 [李琼斯]
