From: patchwork-bot+bluetooth@kernel.org
To: Kiran K <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
chandrashekar.devegowda@intel.com, pmenzel@molgen.mpg.de
Subject: Re: [PATCH v3 1/2] Bluetooth: btintel_pcie: Add Bluetooth core/platform as comments
Date: Mon, 28 Jul 2025 18:40:06 +0000 [thread overview]
Message-ID: <175372800699.807848.11069796095738081245.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250728154910.1428086-1-kiran.k@intel.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 28 Jul 2025 21:19:08 +0530 you wrote:
> Add Bluetooth CNVi core and platform names to the PCI device table for
> each device ID as a comment.
>
> Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
> Signed-off-by: Kiran K <kiran.k@intel.com>
> ---
> changes in v3:
> - Include product and platform name in commit message
> - s/commnents/comments/g
>
> [...]
Here is the summary with links:
- [v3,1/2] Bluetooth: btintel_pcie: Add Bluetooth core/platform as comments
https://git.kernel.org/bluetooth/bluetooth-next/c/ca4d74a68c46
- [v3,2/2] Bluetooth: btintel_pcie: Add id of Scorpious, Panther Lake-H484
(no matching commit)
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-07-28 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 15:49 [PATCH v3 1/2] Bluetooth: btintel_pcie: Add Bluetooth core/platform as comments Kiran K
2025-07-28 15:49 ` [PATCH v3 2/2] Bluetooth: btintel_pcie: Add id of Scorpious, Panther Lake-H484 Kiran K
2025-07-28 16:06 ` [v3,1/2] Bluetooth: btintel_pcie: Add Bluetooth core/platform as comments bluez.test.bot
2025-07-28 18:30 ` [PATCH v3 1/2] " patchwork-bot+bluetooth
2025-07-28 18:40 ` 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=175372800699.807848.11069796095738081245.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chandrashekar.devegowda@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=ravishankar.srivatsa@intel.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 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.