From: patchwork-bot+bluetooth@kernel.org
To: Vaibhav Gupta <vaibhavgupta40@gmail.com>
Cc: sven@kernel.org, j@jannau.net, marcel@holtmann.org,
luiz.dentz@gmail.com, neal@gompa.dev, asahi@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: hci_bcm4377: Use generic power management
Date: Wed, 17 Dec 2025 21:50:08 +0000 [thread overview]
Message-ID: <176600820854.2253459.7299265804546328634.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251210232115.547729-1-vaibhavgupta40@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 10 Dec 2025 23:21:09 +0000 you wrote:
> Switch to the generic PCI power management framework and remove legacy
> callbacks like .suspend() and .resume(). With the generic framework, the
> standard PCI related work like:
> - pci_save/restore_state()
> - pci_enable/disable_device()
> - pci_set_power_state()
> is handled by the PCI core and this driver should implement only
> hci_bcm4377 specific operations in its respective callback functions.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: hci_bcm4377: Use generic power management
https://git.kernel.org/bluetooth/bluetooth-next/c/0ad59c87f41c
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-12-17 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 21:17 [PATCH v1 1/2] Bluetooth: hci_bcm4377: Use generic power management Vaibhav Gupta
2025-12-10 22:05 ` [v1,1/2] " bluez.test.bot
2025-12-10 23:21 ` [PATCH v2] " Vaibhav Gupta
2025-12-11 0:00 ` [v2] " bluez.test.bot
2025-12-17 21:50 ` 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=176600820854.2253459.7299265804546328634.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=asahi@lists.linux.dev \
--cc=j@jannau.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=neal@gompa.dev \
--cc=sven@kernel.org \
--cc=vaibhavgupta40@gmail.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;
as well as URLs for NNTP newsgroup(s).