From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Lee Jones <lee@kernel.org>
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: Thu, 26 Jan 2023 11:01:41 +0100 [thread overview]
Message-ID: <60d87ac5-ddd6-706d-e13a-3431024bca88@linaro.org> (raw)
In-Reply-To: <CABBYNZJEU-GD5J6K8_Ur4PWLvP10VNJGP7e_43H0=W3DOS=PNw@mail.gmail.com>
On 25/01/2023 20:23, Luiz Augusto von Dentz wrote:
>>>> 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, not to
dt-bindings patches are supposed to go via subsystem (with drivers) or
as fallback via Rob's DT tree. The subsystem here is LED, so the patches
should be picked by Pavel and Lee, as maintainers of LED subsystem.
If the subsystem was Bluetooth, then the patch would be for you. I hope
that clarifies.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-26 10:01 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
2023-01-26 10:01 ` Krzysztof Kozlowski [this message]
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=60d87ac5-ddd6-706d-e13a-3431024bca88@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jacek.anaszewski@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.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).