netdev - Re: [PATCH v2] dt-bindings: net: broadcom-bluetooth: Add CYW43439 DT binding

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Mon, 29 Apr 2024 22:44:29 +0200
From: Marek Vasut <marex@...x.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
 linux-bluetooth@...r.kernel.org, Marcel Holtmann <marcel@...tmann.org>
Cc: "David S. Miller" <davem@...emloft.net>,
 Conor Dooley <conor+dt@...nel.org>, Eric Dumazet <edumazet@...gle.com>,
 Jakub Kicinski <kuba@...nel.org>,
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
 Linus Walleij <linus.walleij@...aro.org>,
 Luiz Augusto von Dentz <luiz.dentz@...il.com>,
 Paolo Abeni <pabeni@...hat.com>, Rob Herring <robh@...nel.org>,
 devicetree@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH v2] dt-bindings: net: broadcom-bluetooth: Add CYW43439 DT
 binding

On 4/29/24 8:22 PM, Krzysztof Kozlowski wrote:
> On 29/04/2024 17:10, Marek Vasut wrote:
>> On 3/19/24 6:41 AM, Krzysztof Kozlowski wrote:
>>> On 19/03/2024 05:20, Marek Vasut wrote:
>>>> CYW43439 is a Wi-Fi + Bluetooth combo device from Infineon.
>>>> The Bluetooth part is capable of Bluetooth 5.2 BR/EDR/LE .
>>>> This chip is present e.g. on muRata 1YN module.
>>>>
>>>> Extend the binding with its DT compatible using fallback
>>>> compatible string to "brcm,bcm4329-bt" which seems to be
>>>> the oldest compatible device. This should also prevent the
>>>> growth of compatible string tables in drivers. The existing
>>>> block of compatible strings is retained.
>>>>
>>>> Signed-off-by: Marek Vasut <marex@...x.de>
>>>
>>> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
>>
>> Is there any action necessary from me to get this applied ?
> 
> I recommend resending with proper PATCH prefix matching net-next
> expectations.

I don't think bluetooth is net-next , it has its own ML and its own 
'Bluetooth:' subject prefix. Its patchwork.k.o project also doesn't seem 
to contain many patches with 'net'/'net-next' prefix. Also DT bindings 
do not seem to use it per 'git log 
Documentation/devicetree/bindings/net/bluetooth/'. But the bot is 
complaining about the prefix. Hence my confusion.