linux-kernel - Re: [PATCH v3 2/2] Bluetooth: qca: add QCC2072 support

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]

Message-ID: <a1597998-f996-41e7-b100-3fd20d1130c3@oss.qualcomm.com>
Date: Wed, 11 Feb 2026 12:10:41 +0530
From: Vivek Sahu <vivek.sahu@....qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@....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 2/11/2026 7:18 AM, Dmitry Baryshkov wrote:
> On Tue, 10 Feb 2026 at 15:53, Vivek Sahu <vivek.sahu@....qualcomm.com> wrote:
>>
>>
>>
>> On 2/10/2026 5:46 PM, Dmitry Baryshkov wrote:
>>> 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?
>>>
>> this change includes driver change and yaml change. In recent
>> bluetooth-next branch there is a new style of documentation of bindings
>> comes as "Split to separate schema". I need to re-modify my patch again
>> and compile. Splitting patch seems more convenient for code submission
>> and addressing review comments.
> 
> It makes maintainer's life more complicated as they have to cope with
> dependencies between patch series.
> 
I understand, let me see if i could send the patches in single series.