public inbox for linux-kernel@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, wt@penguintechs.org,
	dmitry.baryshkov@linaro.org, luiz.von.dentz@intel.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	bartosz.golaszewski@linaro.org
Subject: Re: [PATCH 0/3] Bluetooth: hci_qca: fix post merge window regressions
Date: Thu, 01 Aug 2024 08:20:34 +0000	[thread overview]
Message-ID: <172250043460.11616.3564241762852213894.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240731-hci_qca_fixes-v1-0-59dad830b243@linaro.org>

Hello:

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

On Wed, 31 Jul 2024 17:20:47 +0200 you wrote:
> Here are the fixes for regressions reported by Wren and Dmitry. I could
> reproduce the crash on db820c and so I was able to test it but patch 2/3
> could use a Tested-by from Wren on QCA6390.
> 
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
> Bartosz Golaszewski (3):
>       Bluetooth: hci_qca: don't call pwrseq_power_off() twice for QCA6390
>       Bluetooth: hci_qca: fix QCA6390 support on non-DT platforms
>       Bluetooth: hci_qca: fix a NULL-pointer derefence at shutdown
> 
> [...]

Here is the summary with links:
  - [1/3] Bluetooth: hci_qca: don't call pwrseq_power_off() twice for QCA6390
    https://git.kernel.org/bluetooth/bluetooth-next/c/3c9b2c902da0
  - [2/3] Bluetooth: hci_qca: fix QCA6390 support on non-DT platforms
    https://git.kernel.org/bluetooth/bluetooth-next/c/786cd197c92b
  - [3/3] Bluetooth: hci_qca: fix a NULL-pointer derefence at shutdown
    https://git.kernel.org/bluetooth/bluetooth-next/c/9fba2e3f4ac1

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-08-01  8:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31 15:20 [PATCH 0/3] Bluetooth: hci_qca: fix post merge window regressions Bartosz Golaszewski
2024-07-31 15:20 ` [PATCH 1/3] Bluetooth: hci_qca: don't call pwrseq_power_off() twice for QCA6390 Bartosz Golaszewski
2024-07-31 15:20 ` [PATCH 2/3] Bluetooth: hci_qca: fix QCA6390 support on non-DT platforms Bartosz Golaszewski
2024-08-01  7:29   ` Paul Menzel
2024-08-01  7:39     ` Bartosz Golaszewski
2024-08-07 19:09   ` Wren Turkal
2024-08-08  7:49     ` Bartosz Golaszewski
2024-07-31 15:20 ` [PATCH 3/3] Bluetooth: hci_qca: fix a NULL-pointer derefence at shutdown Bartosz Golaszewski
2024-08-06 22:44   ` Nícolas F. R. A. Prado
2024-08-07  7:53     ` Bartosz Golaszewski
2024-08-07 15:03       ` Luiz Augusto von Dentz
2024-08-07 18:34         ` Nícolas F. R. A. Prado
2024-07-31 16:32 ` [PATCH 0/3] Bluetooth: hci_qca: fix post merge window regressions Luiz Augusto von Dentz
2024-08-01  3:57   ` Wren Turkal
2024-08-01  7:23     ` Wren Turkal
2024-08-01  8: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=172250043460.11616.3564241762852213894.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=marcel@holtmann.org \
    --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