From: patchwork-bot+bluetooth@kernel.org
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v3 0/2] More CONFIG_PM* simplifications
Date: Tue, 20 Jan 2026 18:20:05 +0000 [thread overview]
Message-ID: <176893320510.555371.12355664459156628417.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260119123537.2611794-1-hadess@hadess.net>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 19 Jan 2026 13:34:58 +0100 you wrote:
> Follow-up from the earlier "Bluetooth: btusb: Use pm_ptr instead of
> #ifdef CONFIG_PM" patch.
>
> Both drivers were successfully compiled with CONFIG_PM disabled.
>
> Changes since v2:
> - Drop btmtksdio.c changes, there's a fix in bluetooth-next
>
> [...]
Here is the summary with links:
- [v3,1/2] Bluetooth: btnxpuart: Remove unneeded CONFIG_PM ifdef
https://git.kernel.org/bluetooth/bluetooth-next/c/854aa613b6b3
- [v3,2/2] Bluetooth: btintel: Remove unneeded CONFIG_PM* #ifdef's
https://git.kernel.org/bluetooth/bluetooth-next/c/ba93b539e8d4
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-01-20 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 12:34 [PATCH v3 0/2] More CONFIG_PM* simplifications Bastien Nocera
2026-01-19 12:34 ` [PATCH v3 1/2] Bluetooth: btnxpuart: Remove unneeded CONFIG_PM ifdef Bastien Nocera
2026-01-19 14:02 ` More CONFIG_PM* simplifications bluez.test.bot
2026-01-20 6:40 ` [PATCH v3 1/2] Bluetooth: btnxpuart: Remove unneeded CONFIG_PM ifdef Neeraj Sanjay Kale
2026-01-19 12:35 ` [PATCH v3 2/2] Bluetooth: btintel: Remove unneeded CONFIG_PM* #ifdef's Bastien Nocera
2026-01-20 18: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=176893320510.555371.12355664459156628417.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.