From: patchwork-bot+bluetooth@kernel.org
To: Sai Teja Aluvala <aluvala.sai.teja@intel.com>
Cc: linux-bluetooth@vger.kernel.org, kiran.k@intel.com,
chethan.tumkur.narayan@intel.com
Subject: Re: [PATCH v5 0/2] Bluetooth: btintel_pcie: debug INI rework and fatal error injection
Date: Wed, 04 Nov 2026 16:30:07 +0000 [thread overview]
Message-ID: <179380980731.2929236.900247427168680792.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261104122508.241477-1-aluvala.sai.teja@intel.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 4 Nov 2026 17:55:06 +0530 you wrote:
> This series moves the btintel_pcie debug INI parsing into the debug
> file and adds a test mode for injecting firmware exceptions.
>
> Patch 1 moves the debug INI parser (DBG_PATH, ENABLE_INI, LOG_MASK)
> from btintel_pcie.c to btintel_pcie_debug.c, so that all debug INI
> handling lives in one file. The parsing behaviour is unchanged.
>
> [...]
Here is the summary with links:
- [v5,1/2] Bluetooth: btintel_pcie: Move debug INI parsing to debug file
https://git.kernel.org/bluetooth/bluetooth-next/c/ac2656defdd7
- [v5,2/2] Bluetooth: btintel_pcie: Add fatal error injection test mode
https://git.kernel.org/bluetooth/bluetooth-next/c/d81a15edf4ab
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-11-04 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 12:25 [PATCH v5 0/2] Bluetooth: btintel_pcie: debug INI rework and fatal error injection Sai Teja Aluvala
2026-11-04 12:25 ` [PATCH v5 1/2] Bluetooth: btintel_pcie: Move debug INI parsing to debug file Sai Teja Aluvala
2026-11-04 16:43 ` Bluetooth: btintel_pcie: debug INI rework and fatal error injection bluez.test.bot
2026-11-04 12:25 ` [PATCH v5 2/2] Bluetooth: btintel_pcie: Add fatal error injection test mode Sai Teja Aluvala
2026-11-04 16:30 ` 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=179380980731.2929236.900247427168680792.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=aluvala.sai.teja@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 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.