From: patchwork-bot+bluetooth@kernel.org
To: Catherine L <catherine.l@intel.com>
Cc: linux-bluetooth@vger.kernel.org, kiran.k@intel.com,
chethan.tumkur.narayan@intel.com
Subject: Re: [RESEND v1] Bluetooth: btintel_pcie: Add PCI ID for Titan Lake
Date: Tue, 13 Oct 2026 15:10:05 +0000 [thread overview]
Message-ID: <179190420502.367533.6643573344156279406.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261013093650.423572-1-catherine.l@intel.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 13 Oct 2026 15:06:50 +0530 you wrote:
> Add PCI ID 0x9329 for Titan Lake (Scorpius Peak2 C0).
>
> sudo lspci -v -k -d 8086:9329
> 02:00.0 Bluetooth: Intel Corporation Device 9329
> Subsystem: Intel Corporation Device 0012
> Flags: bus master, fast devsel, latency 0, IRQ 16
> Memory at fe000000 (32-bit, non-prefetchable) [size=16K]
> Capabilities: [c8] Power Management version 3
> Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
> Capabilities: [80] MSI-X: Enable+ Count=5 Masked-
> Kernel driver in use: btintel_pcie
> Kernel modules: btintel_pcie
>
> [...]
Here is the summary with links:
- [RESEND,v1] Bluetooth: btintel_pcie: Add PCI ID for Titan Lake
https://git.kernel.org/bluetooth/bluetooth-next/c/88b7183b3945
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-10-13 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 9:36 [RESEND v1] Bluetooth: btintel_pcie: Add PCI ID for Titan Lake Catherine L
2026-10-13 11:55 ` [RESEND,v1] " bluez.test.bot
2026-10-13 15:10 ` 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=179190420502.367533.6643573344156279406.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=catherine.l@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox