public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	krzysztof.kozlowski@linaro.org, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org, bartosz.golaszewski@linaro.org,
	wt@penguintechs.org, quic_zijuhu@quicinc.com
Subject: Re: [PATCH v2] Bluetooth: qca: set power_ctrl_enabled on NULL returned by gpiod_get_optional()
Date: Wed, 24 Apr 2024 15:40:27 +0000	[thread overview]
Message-ID: <171397322792.12898.8815870206676100532.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240424122932.79120-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 Wed, 24 Apr 2024 14:29:32 +0200 you wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> 
> Any return value from gpiod_get_optional() other than a pointer to a
> GPIO descriptor or a NULL-pointer is an error and the driver should
> abort probing. That being said: commit 56d074d26c58 ("Bluetooth: hci_qca:
> don't use IS_ERR_OR_NULL() with gpiod_get_optional()") no longer sets
> power_ctrl_enabled on NULL-pointer returned by
> devm_gpiod_get_optional(). Restore this behavior but bail-out on errors.
> While at it: also bail-out on error returned when trying to get the
> "swctrl" GPIO.
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: qca: set power_ctrl_enabled on NULL returned by gpiod_get_optional()
    https://git.kernel.org/bluetooth/bluetooth-next/c/48a9e64a533b

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



  parent reply	other threads:[~2024-04-24 15:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 12:29 [PATCH v2] Bluetooth: qca: set power_ctrl_enabled on NULL returned by gpiod_get_optional() Bartosz Golaszewski
2024-04-24 12:35 ` quic_zijuhu
2024-04-24 12:59 ` quic_zijuhu
2024-04-24 13:15   ` Wren Turkal
2024-04-24 13:10 ` Wren Turkal
2024-04-24 13:18   ` Bartosz Golaszewski
2024-04-24 13:22     ` quic_zijuhu
2024-04-24 13:31       ` Wren Turkal
2024-04-24 13:36         ` quic_zijuhu
2024-04-24 13:40           ` Wren Turkal
2024-04-24 13:39         ` Bartosz Golaszewski
2024-04-24 13:16 ` [v2] " bluez.test.bot
2024-04-24 14:46 ` [PATCH v2] " Krzysztof Kozlowski
2024-04-24 14:52   ` Bartosz Golaszewski
2024-04-24 15:05     ` Krzysztof Kozlowski
2024-04-24 15:24     ` quic_zijuhu
2024-04-24 15:29       ` quic_zijuhu
2024-04-24 15:31         ` Bartosz Golaszewski
2024-04-24 15:35           ` quic_zijuhu
2024-04-24 15:41             ` Luiz Augusto von Dentz
2024-04-24 15:47               ` quic_zijuhu
2024-04-24 15:57                 ` quic_zijuhu
2024-04-24 15:30       ` Bartosz Golaszewski
2024-04-24 15:31       ` Krzysztof Kozlowski
2024-04-24 15:40 ` patchwork-bot+bluetooth [this message]
2024-04-26 14:37   ` Bartosz Golaszewski
2024-04-26 15:09     ` Luiz Augusto von Dentz
2024-04-26 17:23       ` Bartosz Golaszewski

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=171397322792.12898.8815870206676100532.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --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=quic_zijuhu@quicinc.com \
    --cc=wt@penguintechs.org \
    /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