linux-kernel - Re: [PATCH] Bluetooth: btusb: Fix the patch for MT7920 the affected to MT7921

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: Wed, 8 May 2024 10:33:55 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
 <regressions@...mhuis.info>
To: luiz.dentz@...il.com
Cc: marcel@...tmann.org, johan.hedberg@...il.com, sean.wang@...iatek.com,
 deren.Wu@...iatek.com, chris.lu@...iatek.com, aaron.hou@...iatek.com,
 steve.lee@...iatek.com, linux-bluetooth@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
 patchwork-bot+bluetooth@...nel.org, Peter Tsao <peter.tsao@...iatek.com>,
 Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: [PATCH] Bluetooth: btusb: Fix the patch for MT7920 the affected
 to MT7921

On 16.04.24 17:10, patchwork-bot+bluetooth@...nel.org wrote:
> 
> This patch was applied to bluetooth/bluetooth-next.git (master)
> by Luiz Augusto von Dentz <luiz.von.dentz@...el.com>:
> 
> On Mon, 15 Apr 2024 22:19:22 +0800 you wrote:
>> Because both MT7920 and MT7921 use the same chip ID.
>> We use the 8th bit of fw_flavor to distingush MT7920.
>> The original patch made a mistake to check whole fw_flavor,
>> that makes the condition both true (dev_id == 0x7961 && fw_flavor),
>> and makes MT7921 flow wrong.
>>
>> In this patch, we correct the flow to get the 8th bit value for MT7920.
>> And the patch is verified pass with both MT7920 and MT7921.
>>
>> [...]
> 
> Here is the summary with links:
>   - Bluetooth: btusb: Fix the patch for MT7920 the affected to MT7921
>     https://git.kernel.org/bluetooth/bluetooth-next/c/263296438807

Hi! 6.9 is only days close and this is fixing a 6.9 regression, so allow
me to quickly ask: do you still plan to submit this for mainline merge
soon? Or did you already and I just missed it? Ciao, Thorsten