linux-kernel - Re: [PATCH v1] Bluetooth: qca: Refactor code on the basis of chipset names

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: 
 <177084000433.693413.16945062238265797804.git-patchwork-notify@kernel.org>
Date: Wed, 11 Feb 2026 20:00:04 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Vivek Sahu <vivek.sahu@....qualcomm.com>
Cc: brgl@...nel.org, marcel@...tmann.org, luiz.dentz@...il.com,
 quic_mohamull@...cinc.com, quic_hbandi@...cinc.com,
 linux-arm-msm@...r.kernel.org, linux-bluetooth@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] Bluetooth: qca: Refactor code on the basis of chipset
 names

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@...el.com>:

On Tue, 10 Feb 2026 17:31:01 +0530 you wrote:
> Whenever new chipset support is added to the driver code,
> we ended up adding chipset name to the last of the switch case
> arising code readability issue because of improper sorting of
> the chipset names in various places of the code.
> 
> Refactor code such a way that new chipset can be added easily
> in the code without compromising code readability.
> 
> [...]

Here is the summary with links:
  - [v1] Bluetooth: qca: Refactor code on the basis of chipset names
    https://git.kernel.org/bluetooth/bluetooth-next/c/c2b82511ef7d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html