linux-kernel - Re: [PATCH v3 1/1] Bluetooth: btqca: Add WCN6855 firmware priority selection feature

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 for Android: free password hash cracker in your pocket

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

Message-ID: <7bf64ac2-b793-4343-b6e4-41a88cd1295c@oss.qualcomm.com>
Date: Tue, 18 Nov 2025 15:04:36 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Shuai Zhang <shuai.zhang@....qualcomm.com>,
        Bartosz Golaszewski <brgl@...ev.pl>,
        Marcel Holtmann <marcel@...tmann.org>,
        Luiz Augusto von Dentz <luiz.dentz@...il.com>
Cc: linux-arm-msm@...r.kernel.org, linux-bluetooth@...r.kernel.org,
        linux-kernel@...r.kernel.org, cheng.jiang@....qualcomm.com,
        quic_chezhou@...cinc.com, wei.deng@....qualcomm.com
Subject: Re: [PATCH v3 1/1] Bluetooth: btqca: Add WCN6855 firmware priority
 selection feature

On 11/18/25 2:44 PM, Shuai Zhang wrote:
> Dear
> 
> On 11/17/2025 10:16 AM, Shuai Zhang wrote:
>> Historically, WCN685x and QCA2066 shared the same firmware files.
>> Now, changes are planned for the firmware that will make it incompatible
>> with QCA2066, so a new firmware name is required for WCN685x.
>>
>> Test Steps:
>>   - Boot device
>>   - Check the BTFW loading status via dmesg
>>
>> Sanity pass and Test Log:
>> QCA Downloading qca/wcnhpbftfw21.tlv
>> Direct firmware load for qca/wcnhpbftfw21.tlv failed with error -2
>> QCA Downloading qca/hpbftfw21.tlv
>>
>> Signed-off-by: Shuai Zhang <shuai.zhang@....qualcomm.com>
>> ---

[...]

> Could you confirm if it has already been accepted?

Please familiarize yourself with the kernel development cycle. You sent this
patch yesterday, at a very late point in the kernel dev cycle (rc6, normally
rc7 or rc8 is last) when maintainers generally don't accept patches.

https://docs.kernel.org/process/2.Process.html

The branch your changes will land before being queued for torvalds merge
the following cycle is likely:

https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/log/

which you can watch yourself, although normally maintainers respond with
an "applied, thanks" message

Please also trim your replies, you included a whole patch as context and
only added meaningful text at the very end. Please also don't top-post.
I see you're doing so as a mannerism, but it should generally be avoided.

Konrad