Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-4168-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Precedence: bulk
MIME-Version: 1.0
References: <20240319042058.133885-1-marex@denx.de> <97eeb05d-9fb4-4c78-8d7b-610629ed76b3@linaro.org>
 <93eeb045-b2a3-41d7-a3f2-1df89c588bfd@denx.de> <793d016d-2bde-407a-8300-f42182431eb1@linaro.org>
 <c21823f2-4dd7-490a-8b76-7cab422428ba@denx.de>
In-Reply-To: <c21823f2-4dd7-490a-8b76-7cab422428ba@denx.de>
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date: Mon, 29 Apr 2024 16:57:33 -0400
Message-ID: <CABBYNZJk33ZcKc9EPi+Hmqb-pq3vSSzB3wkS4nJ45dxG6dBMUw@mail.gmail.com>
Subject: Re: [PATCH v2] dt-bindings: net: broadcom-bluetooth: Add CYW43439 DT binding
To: Marek Vasut <marex@denx.de>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, linux-bluetooth@vger.kernel.org, 
	Marcel Holtmann <marcel@holtmann.org>, "David S. Miller" <davem@davemloft.net>, 
	Conor Dooley <conor+dt@kernel.org>, Eric Dumazet <edumazet@google.com>, 
	Jakub Kicinski <kuba@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, 
	Linus Walleij <linus.walleij@linaro.org>, Paolo Abeni <pabeni@redhat.com>, 
	Rob Herring <robh@kernel.org>, devicetree@vger.kernel.org, netdev@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Marek,

On Mon, Apr 29, 2024 at 4:44=E2=80=AFPM Marek Vasut <marex@denx.de> wrote:
>
> 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@denx.de>
> >>>
> >>> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.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.

Well usually we require Bluetooth: prefix to indicate this patch is
for bluetooth/bluetooth-next trees, or you can do via subject e.g.
[bluetooth-next v1...] otherwise it could be merged via other trees.

--=20
Luiz Augusto von Dentz