From: patchwork-bot+bluetooth@kernel.org
To: Max Chou <max.chou@realtek.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, alex_lu@realsil.com.cn,
allen_chen@realsil.com.cn, hildawu@realtek.com,
karenhsu@realtek.com, kidman@realtek.com, mmandlik@google.com,
abhishekpandit@chromium.org, apusaka@chromium.org,
yinghsu@chromium.org, alainmichaud@google.com
Subject: Re: [PATCH v5] Bluetooth: btrtl: Firmware format v2 support
Date: Mon, 17 Apr 2023 18:30:19 +0000 [thread overview]
Message-ID: <168175621917.2755.2479462540235386581.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230417023358.38767-1-max.chou@realtek.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 17 Apr 2023 10:33:58 +0800 you wrote:
> From: Max Chou <max.chou@realtek.com>
>
> Realtek changed the format of the firmware file as v2. The driver
> should implement the patch to extract the firmware data from the
> firmware file. The future chips must apply this patch for firmware loading.
> This patch is compatible with the both previous format and v2 as well.
>
> [...]
Here is the summary with links:
- [v5] Bluetooth: btrtl: Firmware format v2 support
https://git.kernel.org/bluetooth/bluetooth-next/c/0330a285b7f1
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-04-17 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 2:33 max.chou
2023-04-17 18:30 ` 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=168175621917.2755.2479462540235386581.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=abhishekpandit@chromium.org \
--cc=alainmichaud@google.com \
--cc=alex_lu@realsil.com.cn \
--cc=allen_chen@realsil.com.cn \
--cc=apusaka@chromium.org \
--cc=hildawu@realtek.com \
--cc=johan.hedberg@gmail.com \
--cc=karenhsu@realtek.com \
--cc=kidman@realtek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=max.chou@realtek.com \
--cc=mmandlik@google.com \
--cc=yinghsu@chromium.org \
/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®