From: patchwork-bot+bluetooth@kernel.org
To: Ravindra <ravindra@intel.com>
Cc: linux-bluetooth@vger.kernel.org, lsa.uz@pm.me,
vladimirkondratyev2@gmail.com, chethan.tumkur.narayan@intel.com,
kiran.k@intel.com, pmenzel@molgen.mpg.de
Subject: Re: [PATCH v4 4/4] Bluetooth: btintel_pcie: clear the GP0 cause with a W1C write
Date: Tue, 29 Sep 2026 15:10:19 +0000 [thread overview]
Message-ID: <179069461953.983246.6683069872210269524.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260927152356.2886291-1-ravindra@intel.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 27 Sep 2026 20:53:56 +0530 you wrote:
> MSIX_HW_INT_CAUSES is a write-one-to-clear register. Using a
> read-modify-write helper writes zero to GP0, leaving the cause uncleared,
> and can acknowledge unrelated pending causes through the read value.
>
> Write only the GP0 bit directly, matching the interrupt handler's W1C
> acknowledgment convention.
>
> [...]
Here is the summary with links:
- [v4,4/4] Bluetooth: btintel_pcie: clear the GP0 cause with a W1C write
https://git.kernel.org/bluetooth/bluetooth-next/c/6091d2771395
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-09-29 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 15:23 [PATCH v4 4/4] Bluetooth: btintel_pcie: clear the GP0 cause with a W1C write Ravindra
2026-09-27 22:52 ` [v4,4/4] " bluez.test.bot
2026-09-29 15:10 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-26 8:52 [PATCH v4 1/4] Bluetooth: btintel_pcie: fix stale cache in set_dxstate fallback check Ravindra
2026-09-26 8:53 ` [PATCH v4 4/4] Bluetooth: btintel_pcie: clear the GP0 cause with a W1C write Ravindra
2026-09-26 14:45 ` Sergey Lebedev
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=179069461953.983246.6683069872210269524.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lsa.uz@pm.me \
--cc=pmenzel@molgen.mpg.de \
--cc=ravindra@intel.com \
--cc=vladimirkondratyev2@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox