From: patchwork-bot+bluetooth@kernel.org
To: Kiran K <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
chethan.tumkur.narayan@intel.com,
chandrashekar.devegowda@intel.com, vijay.satija@intel.com
Subject: Re: [PATCH v3 1/2] Bluetooth: btintel_pcie: Setup buffers for firmware traces
Date: Wed, 26 Feb 2025 21:10:37 +0000 [thread overview]
Message-ID: <174060423723.846473.4528221555018431128.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250225114311.9514-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 Tue, 25 Feb 2025 17:13:10 +0530 you wrote:
> This patch allocates the host memory which is used by controller to dump
> the firmware traces. The memory needs to be shared with controller via
> context information.
>
> Co-developed-by: Vijay Satija <vijay.satija@intel.com>
> Signed-off-by: Vijay Satija <vijay.satija@intel.com>
> Signed-off-by: Kiran K <kiran.k@intel.com>
>
> [...]
Here is the summary with links:
- [v3,1/2] Bluetooth: btintel_pcie: Setup buffers for firmware traces
https://git.kernel.org/bluetooth/bluetooth-next/c/3104ae5ad1b7
- [v3,2/2] Bluetooth: btintel_pcie: Read hardware exception data
https://git.kernel.org/bluetooth/bluetooth-next/c/978777bfa2d8
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-02-26 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 11:43 [PATCH v3 1/2] Bluetooth: btintel_pcie: Setup buffers for firmware traces Kiran K
2025-02-25 11:43 ` [PATCH v3 2/2] Bluetooth: btintel_pcie: Read hardware exception data Kiran K
2025-02-25 11:54 ` [v3,1/2] Bluetooth: btintel_pcie: Setup buffers for firmware traces bluez.test.bot
2025-02-26 21: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=174060423723.846473.4528221555018431128.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chandrashekar.devegowda@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ravishankar.srivatsa@intel.com \
--cc=vijay.satija@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.