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>,
Deren Wu <deren.Wu@mediatek.com>,
Aaron Hou <aaron.hou@mediatek.com>, KM Lin <km.lin@mediatek.com>,
Robin Chiu <robin.chiu@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] linux-firmware: update firmware for mediatek bluetooth chip (MT7922)
Date: Mon, 27 Nov 2023 12:50:20 +0100 [thread overview]
Message-ID: <e2f67283-90ea-4f74-977d-dde8bdd0a8ea@molgen.mpg.de> (raw)
In-Reply-To: <20231127085827.13060-1-chris.lu@mediatek.com>
Dear Chris,
Thank you for the patch.
Am 27.11.23 um 09:58 schrieb Chris Lu:
> Update binary firmware for MT7922 BT devices.
>
> File: mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin
> Version: 20231120183620
It’d be great if you added the version in the git commit message
summary/title too. The `linux-firmware` prefix is probably redundant. No
idea if a tag exists for it. So, maybe:
mediatek: Update BT MT7921 fw from 20230627144220 to 20231120183620
or
Update Mediatek BT MT7921 fw to 20231120183620
Also, it would be great if you added the change-log to the commit
message, so people have an idea, what improved.
> Signed-off-by: Chris Lu <chris.lu@mediatek.com>
> ---
> WHENCE | 2 +-
> mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin | Bin 512022 -> 513878 bytes
> 2 files changed, 1 insertion(+), 1 deletion(-)
[…]
Kind regards,
Paul
next prev parent reply other threads:[~2023-11-27 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 8:58 [PATCH] linux-firmware: update firmware for mediatek bluetooth chip (MT7922) Chris Lu
2023-11-27 11:50 ` Paul Menzel [this message]
2023-11-27 14:02 ` Josh Boyer
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=e2f67283-90ea-4f74-977d-dde8bdd0a8ea@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=aaron.hou@mediatek.com \
--cc=ben@decadent.org.uk \
--cc=chris.lu@mediatek.com \
--cc=deren.Wu@mediatek.com \
--cc=dwmw2@infradead.org \
--cc=johan.hedberg@gmail.com \
--cc=jwboyer@kernel.org \
--cc=km.lin@mediatek.com \
--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=robin.chiu@mediatek.com \
--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