From: patchwork-bot+bluetooth@kernel.org
To: Sean Wang <sean.wang@kernel.org>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
sean.wang@mediatek.com, pedro.tsai@mediatek.com,
felix.freimann@mediatek.com
Subject: Re: [PATCH] Bluetooth: btmtksdio: Prevent enabling interrupts after IRQ handler removal
Date: Thu, 20 Mar 2025 19:00:45 +0000 [thread overview]
Message-ID: <174249724504.1878155.13264790532381616265.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250312012522.53604-1-sean.wang@kernel.org>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 11 Mar 2025 18:25:22 -0700 you wrote:
> From: Sean Wang <sean.wang@mediatek.com>
>
> Ensure interrupts are not re-enabled when the IRQ handler has already been
> removed. This prevents unexpected IRQ handler execution due to stale or
> unhandled interrupts.
>
> Modify btmtksdio_txrx_work to check if bdev->func->irq_handler exists
> before calling sdio_writel to enable interrupts.
>
> [...]
Here is the summary with links:
- Bluetooth: btmtksdio: Prevent enabling interrupts after IRQ handler removal
https://git.kernel.org/bluetooth/bluetooth-next/c/01c13f057bb7
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-03-20 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 1:25 sean.wang
2025-03-20 19:00 ` 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=174249724504.1878155.13264790532381616265.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=felix.freimann@mediatek.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pedro.tsai@mediatek.com \
--cc=sean.wang@kernel.org \
--cc=sean.wang@mediatek.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
all inboxes | Powered by JetHome®