From: patchwork-bot+bluetooth@kernel.org
To: Zhangchao Zhang <ot_zhangchao.zhang@mediatek.com>
Cc: marcel@holtmann.org, matthias.bgg@gmail.com,
luiz.dentz@gmail.com, angelogioacchino.delregno@collabora.com,
krzk@kernel.org, sean.wang@mediatek.com, deren.Wu@mediatek.com,
chris.lu@mediatek.com, Hao.qin@mediatek.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v9] Bluetooth: mediatek: add gpio pin to reset bt
Date: Mon, 29 Sep 2025 16:10:07 +0000 [thread overview]
Message-ID: <175916220774.1630000.3594430707404440573.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250926101046.26559-1-ot_zhangchao.zhang@mediatek.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 26 Sep 2025 18:10:46 +0800 you wrote:
> Support the platform Bluetooth to be reset by hardware pin,
> when a Bluetooth exception occurs, attempt to reset the
> Bluetooth module using the hardware reset pin, as this
> method is generally more stable and reliable than a
> software reset. If the hardware reset pin is not specified
> in the device tree, fall back to the existing software
> reset mechanism to ensure backward compatibility.
>
> [...]
Here is the summary with links:
- [v9] Bluetooth: mediatek: add gpio pin to reset bt
https://git.kernel.org/bluetooth/bluetooth-next/c/8fe90a5ad3d9
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-09-29 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 10:10 [PATCH v9] Bluetooth: mediatek: add gpio pin to reset bt Zhangchao Zhang
2025-09-29 10:40 ` AngeloGioacchino Del Regno
2025-09-29 16:10 ` 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=175916220774.1630000.3594430707404440573.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=Hao.qin@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chris.lu@mediatek.com \
--cc=deren.Wu@mediatek.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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=matthias.bgg@gmail.com \
--cc=ot_zhangchao.zhang@mediatek.com \
--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.