Search Linux Wireless

Re: [PATCH v2] dt-bindings: leds: Document Bluetooth and WLAN triggers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

> > not to mention this was submitted to linux-bluetooth and nobody else
> > other than Rob reviewed it,
>
> To: Pavel Machek <pavel@xxxxxx>, Lee Jones <lee@xxxxxxxxxx>,
>     Rob Herring <robh+dt@xxxxxxxxxx>,
>     Krzysztof Kozlowski <krzysztof.kozlowski+dt@xxxxxxxxxx>,
>     Jacek Anaszewski <jacek.anaszewski@xxxxxxxxx>
> Cc: linux-leds@xxxxxxxxxxxxxxx, devicetree@xxxxxxxxxxxxxxx,
>     linux-wireless@xxxxxxxxxxxxxxx, linux-bluetooth@xxxxxxxxxxxxxxx,
>     linux-renesas-soc@xxxxxxxxxxxxxxx,
>     Geert Uytterhoeven <geert+renesas@xxxxxxxxx>,
>     Rob Herring <robh@xxxxxxxxxx>
>
> > anyway I'd be happy if the dt-bindings patches
> > would be handled elsewhere.
>
> Yep, we got this. :)

So if it starts with dt-binding: prefix shall we ignore? Or is just
for dt-bindings: leds? Or perhaps we can just ignore patches received
as CC: rather than directly To: field.

>
> --
> Lee Jones [李琼斯]



-- 
Luiz Augusto von Dentz




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Wireless Regulations]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux