From: patchwork-bot+bluetooth@kernel.org
To: Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>
Cc: linux-bluetooth@vger.kernel.org,
chethan.tumkur.narayan@intel.com, kiran.k@intel.com,
aluvala.sai.teja@intel.com, pmenzel@molgen.mpg.de
Subject: Re: [PATCH v2] Bluetooth: btintel_pcie: Fix SCP DBGC base address
Date: Wed, 11 Nov 2026 20:20:07 +0000 [thread overview]
Message-ID: <179442840742.1623293.17516886836216832680.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261111141822.2888893-1-chandrashekar.devegowda@intel.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 11 Nov 2026 19:48:22 +0530 you wrote:
> BTINTEL_PCIE_DBGC_BASE_ADDR_SCP was entered as 0xf0d5d500 by mistake
> when the define was added. The base of the SCP debug controller is
> 0xf0d5d400, as documented in the Intel SCP SAS document, so the value
> is one register row too high. The status and wrap-around registers
> derived from it at offsets 0x1C and 0x2C therefore point at the wrong
> addresses, and the debug buffer status and wrap-around state read while
> dumping SCP debug traces are incorrect.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: btintel_pcie: Fix SCP DBGC base address
https://git.kernel.org/bluetooth/bluetooth-next/c/1752a2c40059
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-11 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 6:45 [PATCH v1] Bluetooth: btintel_pcie: Fix SCP DBGC base address Chandrashekar Devegowda
2026-11-04 7:05 ` Paul Menzel
2026-11-06 9:44 ` Devegowda, Chandrashekar
2026-11-04 8:35 ` [v1] " bluez.test.bot
2026-11-11 14:18 ` [PATCH v2] " Chandrashekar Devegowda
2026-11-11 18:22 ` [v2] " bluez.test.bot
2026-11-11 20:20 ` 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=179442840742.1623293.17516886836216832680.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=aluvala.sai.teja@intel.com \
--cc=chandrashekar.devegowda@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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