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
Subject: Re: [PATCH v5 1/5] Bluetooth: btmtk: add the function to get the fw name
Date: Mon, 20 May 2024 19:40:32 +0000 [thread overview]
Message-ID: <171623403235.10216.9445226154249031065.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ce0337178bf617d52ff320a36837d75bf537df2d.1715813148.git.sean.wang@kernel.org>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 15 May 2024 16:15:17 -0700 you wrote:
> From: Sean Wang <sean.wang@mediatek.com>
>
> Include a shared function to get the firmware name, to prevent repeating
> code for similar chipsets.
>
> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
>
> [...]
Here is the summary with links:
- [v5,1/5] Bluetooth: btmtk: add the function to get the fw name
https://git.kernel.org/bluetooth/bluetooth-next/c/1a9f00aa23b8
- [v5,2/5] Bluetooth: btmtk: apply the common btmtk_fw_get_filename
https://git.kernel.org/bluetooth/bluetooth-next/c/8a5b9ee69fe6
- [v5,3/5] Bluetooth: btusb: mediatek: refactor the function btusb_mtk_reset
https://git.kernel.org/bluetooth/bluetooth-next/c/9d5a3b40987d
- [v5,4/5] Bluetooth: btusb: mediatek: reset the controller before downloading the fw
https://git.kernel.org/bluetooth/bluetooth-next/c/8f9fa6c70d35
- [v5,5/5] Bluetooth: btusb: mediatek: add MT7922 subsystem reset
https://git.kernel.org/bluetooth/bluetooth-next/c/2a6bc5724952
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:[~2024-05-20 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 23:15 [PATCH v5 1/5] Bluetooth: btmtk: add the function to get the fw name sean.wang
2024-05-15 23:15 ` [PATCH v5 2/5] Bluetooth: btmtk: apply the common btmtk_fw_get_filename sean.wang
2024-05-15 23:15 ` [PATCH v5 3/5] Bluetooth: btusb: mediatek: refactor the function btusb_mtk_reset sean.wang
2024-05-15 23:15 ` [PATCH v5 4/5] Bluetooth: btusb: mediatek: reset the controller before downloading the fw sean.wang
2024-05-15 23:15 ` [PATCH v5 5/5] Bluetooth: btusb: mediatek: add MT7922 subsystem reset sean.wang
2024-05-15 23:56 ` [v5,1/5] Bluetooth: btmtk: add the function to get the fw name bluez.test.bot
2024-05-20 19:40 ` 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=171623403235.10216.9445226154249031065.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--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=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