[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e2f67283-90ea-4f74-977d-dde8bdd0a8ea@molgen.mpg.de>
Date:   Mon, 27 Nov 2023 12:50:20 +0100
From:   Paul Menzel <pmenzel@...gen.mpg.de>
To:     Chris Lu <chris.lu@...iatek.com>
Cc:     Josh Boyer <jwboyer@...nel.org>,
        David Woodhouse <dwmw2@...radead.org>,
        Ben Hutchings <ben@...adent.org.uk>,
        Marcel Holtmann <marcel@...tmann.org>,
        Johan Hedberg <johan.hedberg@...il.com>,
        Sean Wang <sean.wang@...iatek.com>,
        Deren Wu <deren.Wu@...iatek.com>,
        Aaron Hou <aaron.hou@...iatek.com>,
        KM Lin <km.lin@...iatek.com>,
        Robin Chiu <robin.chiu@...iatek.com>,
        Steve Lee <steve.lee@...iatek.com>,
        linux-bluetooth@...r.kernel.org, linux-firmware@...nel.org,
        linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH] linux-firmware: update firmware for mediatek bluetooth
 chip (MT7922)
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@...iatek.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
Powered by blists - more mailing lists