From: patchwork-bot+bluetooth@kernel.org
To: Vivek Sahu <vivek.sahu@oss.qualcomm.com>
Cc: brgl@kernel.org, marcel@holtmann.org, luiz.dentz@gmail.com,
quic_mohamull@quicinc.com, quic_hbandi@quicinc.com,
linux-arm-msm@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: qca: Refactor code on the basis of chipset names
Date: Wed, 11 Feb 2026 20:00:04 +0000 [thread overview]
Message-ID: <177084000433.693413.16945062238265797804.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260210120101.1046091-1-vivek.sahu@oss.qualcomm.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.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
prev parent reply other threads:[~2026-02-11 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 12:01 [PATCH v1] Bluetooth: qca: Refactor code on the basis of chipset names Vivek Sahu
2026-02-10 12:13 ` Dmitry Baryshkov
2026-02-10 13:21 ` [v1] " bluez.test.bot
2026-02-11 20:00 ` patchwork-bot+bluetooth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177084000433.693413.16945062238265797804.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=brgl@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=quic_hbandi@quicinc.com \
--cc=quic_mohamull@quicinc.com \
--cc=vivek.sahu@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox