From: patchwork-bot+bluetooth@kernel.org
To: Ismail Tarim <ismailtarim7@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, jing.cai@mediatek.com,
sean.wang@mediatek.com, chris.lu@mediatek.com,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Bluetooth: btmtk: fix subsystem reset error reporting
Date: Mon, 17 Aug 2026 19:46:00 +0000 [thread overview]
Message-ID: <178699596038.1691257.10089072145797162594.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260815115624.8309-1-ismailtarim7@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 15 Aug 2026 14:56:22 +0300 you wrote:
> Two bugs in btmtk_usb_subsys_reset() that make it report success to its
> caller when the subsystem reset has actually failed.
>
> Patch 1 covers the case where the post-reset chip id reads back as zero:
> the function logs "subsys reset fail." and then returns 0.
>
> Patch 2 restores propagation of the MTK_BT_RST_DONE poll timeout, which
> has been silently overwritten since commit 3dcb122b3064 ("Bluetooth:
> btusb: mediatek: return error for failed reg access") started assigning
> err at the chip id read.
>
> [...]
Here is the summary with links:
- [v2,1/2] Bluetooth: btmtk: Do not report success when subsys reset fails
https://git.kernel.org/bluetooth/bluetooth-next/c/771e812f94b3
- [v2,2/2] Bluetooth: btmtk: Do not discard the subsystem reset timeout
https://git.kernel.org/bluetooth/bluetooth-next/c/54c03e6bc718
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-08-17 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 11:56 [PATCH v2 0/2] Bluetooth: btmtk: fix subsystem reset error reporting Ismail Tarim
2026-08-15 11:56 ` [PATCH v2 1/2] Bluetooth: btmtk: Do not report success when subsys reset fails Ismail Tarim
2026-08-15 12:36 ` Bluetooth: btmtk: fix subsystem reset error reporting bluez.test.bot
2026-08-15 11:56 ` [PATCH v2 2/2] Bluetooth: btmtk: Do not discard the subsystem reset timeout Ismail Tarim
2026-08-17 19:46 ` 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=178699596038.1691257.10089072145797162594.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chris.lu@mediatek.com \
--cc=ismailtarim7@gmail.com \
--cc=jing.cai@mediatek.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=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 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.