From: patchwork-bot+bluetooth@kernel.org
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
krzysztof.kozlowski@linaro.org, chharry@google.com,
bgodavar@qti.qualcomm.com, jiatingw@qti.qualcomm.com,
vincentch@google.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, bartosz.golaszewski@linaro.org,
stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_qca: move the SoC type check to the right place
Date: Tue, 27 May 2025 13:20:31 +0000 [thread overview]
Message-ID: <174835203174.1634553.14732152604532181599.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250527074737.21641-1-brgl@bgdev.pl>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 27 May 2025 09:47:37 +0200 you wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> Commit 3d05fc82237a ("Bluetooth: qca: set power_ctrl_enabled on NULL
> returned by gpiod_get_optional()") accidentally changed the prevous
> behavior where power control would be disabled without the BT_EN GPIO
> only on QCA_WCN6750 and QCA_WCN6855 while also getting the error check
> wrong. We should treat every IS_ERR() return value from
> devm_gpiod_get_optional() as a reason to bail-out while we should only
> set power_ctrl_enabled to false on the two models mentioned above. While
> at it: use dev_err_probe() to save a LOC.
>
> [...]
Here is the summary with links:
- Bluetooth: hci_qca: move the SoC type check to the right place
https://git.kernel.org/bluetooth/bluetooth-next/c/8df2c74d466c
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:[~2025-05-27 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 7:47 [PATCH] Bluetooth: hci_qca: move the SoC type check to the right place Bartosz Golaszewski
2025-05-27 8:02 ` Krzysztof Kozlowski
2025-05-27 8:39 ` bluez.test.bot
2025-05-27 9:04 ` [PATCH] " Hsin-chen Chuang
2025-05-27 13:20 ` 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=174835203174.1634553.14732152604532181599.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=bgodavar@qti.qualcomm.com \
--cc=brgl@bgdev.pl \
--cc=chharry@google.com \
--cc=jiatingw@qti.qualcomm.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=stable@vger.kernel.org \
--cc=vincentch@google.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