From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Chris Lu <chris.lu@mediatek.com>
Cc: Josh Boyer <jwboyer@kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Ben Hutchings <ben@decadent.org.uk>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Sean Wang <sean.wang@mediatek.com>,
Allan Wang <allan.wang@mediatek.com>,
Aaron Hou <aaron.hou@mediatek.com>,
Steve Lee <steve.lee@mediatek.com>,
linux-bluetooth@vger.kernel.org, linux-firmware@kernel.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v1] linux-firmware: update firmware for mediatek bluetooth chip (MT7920)
Date: Fri, 8 Nov 2024 09:37:44 +0100 [thread overview]
Message-ID: <46444b60-2d1a-45c2-9a96-8352d1879516@molgen.mpg.de> (raw)
In-Reply-To: <20241108082515.19817-1-chris.lu@mediatek.com>
Dear Chris,
Thank you for your patch. Maybe include the version in the
summary/title? `linux-firmware` also seems redundant. Maybe:
mediatek MT7920: Update BT_RAM_CODE_MT7961_1a_2_hdr to 20241104091246
mediatek MT7920: Update BT_RAM_CODE_MT7961_1a_2_hdr from 20240930111457
to 20241104091246
Am 08.11.24 um 09:25 schrieb Chris Lu:
> Update binary firmware for MT7920 BT devices.
>
> File: mediatek/BT_RAM_CODE_MT7961_1a_2_hdr.bin
The summary says MT7920, but the file name has MT7961. Is MT7961 a part
of MT7920?
> Version: 20241104091246
It’d be great if you added a change-log.
> Signed-off-by: Chris Lu <chris.lu@mediatek.com>
> ---
> WHENCE | 2 +-
> mediatek/BT_RAM_CODE_MT7961_1a_2_hdr.bin | Bin 493809 -> 493809 bytes
> 2 files changed, 1 insertion(+), 1 deletion(-)
Kind regards,
Paul
next prev parent reply other threads:[~2024-11-08 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 8:25 Chris Lu
2024-11-08 8:37 ` Paul Menzel [this message]
2024-11-08 9:25 ` Chris Lu (陸稚泓)
2024-11-08 9:53 ` Paul Menzel
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=46444b60-2d1a-45c2-9a96-8352d1879516@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=aaron.hou@mediatek.com \
--cc=allan.wang@mediatek.com \
--cc=ben@decadent.org.uk \
--cc=chris.lu@mediatek.com \
--cc=dwmw2@infradead.org \
--cc=johan.hedberg@gmail.com \
--cc=jwboyer@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=marcel@holtmann.org \
--cc=sean.wang@mediatek.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
all inboxes | Powered by JetHome®