From: patchwork-bot+bluetooth@kernel.org
To: Sean Wang <sean.wang@mediatek.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, chris.lu@mediatek.com,
Soul.Huang@mediatek.com, Leon.Yen@mediatek.com,
Deren.Wu@mediatek.com, km.lin@mediatek.com,
robin.chiu@mediatek.com, Eddie.Chen@mediatek.com,
ch.yeh@mediatek.com, jenhao.yang@mediatek.com,
Stella.Chang@mediatek.com, Tom.Chou@mediatek.com,
steve.lee@mediatek.com, jsiuda@google.com, frankgor@google.com,
abhishekpandit@google.com, michaelfsun@google.com,
mmandlik@google.com, abhishekpandit@chromium.org,
mcchou@chromium.org, shawnku@google.com,
linux-bluetooth@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 1/3] Bluetooth: btusb: mediatek: readx_poll_timeout replaces open coding
Date: Thu, 29 Jun 2023 19:24:43 +0000 [thread overview]
Message-ID: <168806668365.29593.2167157062342737212.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <80efe66b16d933e3457bd38b1a60a5d51d4dee9e.1687991820.git.objelf@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 29 Jun 2023 06:54:55 +0800 you wrote:
> From: Sean Wang <sean.wang@mediatek.com>
>
> Use readx_poll_timeout instead of open coding to poll the hardware reset
> status until it is done.
>
> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
>
> [...]
Here is the summary with links:
- [v8,1/3] Bluetooth: btusb: mediatek: readx_poll_timeout replaces open coding
https://git.kernel.org/bluetooth/bluetooth-next/c/c56e5f834e13
- [v8,2/3] Bluetooth: btmtk: introduce btmtk reset work
https://git.kernel.org/bluetooth/bluetooth-next/c/ed2e80b8b6a7
- [v8,3/3] Bluetooth: btusb: mediatek: add MediaTek devcoredump support
https://git.kernel.org/bluetooth/bluetooth-next/c/872f8c253cb9
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:[~2023-06-29 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 22:54 [PATCH v8 1/3] Bluetooth: btusb: mediatek: readx_poll_timeout replaces open coding sean.wang
2023-06-28 22:54 ` [PATCH v8 2/3] Bluetooth: btmtk: introduce btmtk reset work sean.wang
2023-06-28 22:54 ` [PATCH v8 3/3] Bluetooth: btusb: mediatek: add MediaTek devcoredump support sean.wang
2023-06-29 19:24 ` 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=168806668365.29593.2167157062342737212.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=Deren.Wu@mediatek.com \
--cc=Eddie.Chen@mediatek.com \
--cc=Leon.Yen@mediatek.com \
--cc=Soul.Huang@mediatek.com \
--cc=Stella.Chang@mediatek.com \
--cc=Tom.Chou@mediatek.com \
--cc=abhishekpandit@chromium.org \
--cc=abhishekpandit@google.com \
--cc=ch.yeh@mediatek.com \
--cc=chris.lu@mediatek.com \
--cc=frankgor@google.com \
--cc=jenhao.yang@mediatek.com \
--cc=johan.hedberg@gmail.com \
--cc=jsiuda@google.com \
--cc=km.lin@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=mcchou@chromium.org \
--cc=michaelfsun@google.com \
--cc=mmandlik@google.com \
--cc=robin.chiu@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shawnku@google.com \
--cc=steve.lee@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