[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <erc5u6hzofidlf54dsz7htta55o4xwgihgh4tu6mqkg2ijz3fo@6hd6q6iljrfq>
Date: Tue, 10 Feb 2026 14:16:28 +0200
From: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
To: Vivek Sahu <vivek.sahu@....qualcomm.com>
Cc: Bartosz Golaszewski <brgl@...nel.org>, quic_mohamull@...cinc.com,
quic_hbandi@...cinc.com, linux-bluetooth@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, Marcel Holtmann <marcel@...tmann.org>,
Luiz Augusto von Dentz <luiz.dentz@...il.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Balakrishna Godavarthi <quic_bgodavar@...cinc.com>,
Rocky Liao <quic_rjliao@...cinc.com>
Subject: Re: [PATCH v3 2/2] Bluetooth: qca: add QCC2072 support
On Tue, Feb 10, 2026 at 05:41:13PM +0530, Vivek Sahu wrote:
>
> On 2/9/2026 5:04 PM, Bartosz Golaszewski wrote:
> > On Mon, 9 Feb 2026 09:06:13 +0100, Vivek Sahu
> > <vivek.sahu@....qualcomm.com> said:
> > > QCC2072 is a family of WiFi/BT connectivity chip.
> > > It requires different firmware files and has different
> > > configurations , so add it as a separate SoC type.
> > >
> > > Correct the sorting of other chipsets for better readability.
> > >
> > > The firmware for these chips has been recently added to the
> > > linux-firmware repository and will be a part of the upcoming
> > > release.
> > Something is wrong with formatting here.
> >
> > I would personally split the sorting and support for the new model into two
> > patches - without and with functional changes respectively - for easier review.
> >
> > Bartosz
>
> Yes, I'm now splitting this patch into 2 parts, one for sorting another one
> for new model
>
> support. Please ignore this patch.
Please stop adding extra empty lines between (or fix your email client).
>
> Sorting change has been raised with tittle "[PATCH v1] Bluetooth: qca:
> Refactor code on
>
> the basis of chipset names". Please approve it at quickest so that we can
> raise new model
>
> addition code changes on top of that.
Why couldn't you send it as 2 patches in a single series?
--
With best wishes
Dmitry
Powered by blists - more mailing lists