From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.molgen.mpg.de (mx3.molgen.mpg.de [141.14.17.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 676C81DF271; Fri, 8 Nov 2024 08:38:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=141.14.17.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1731055117; cv=none; b=MA9zqpY1HAsTToMtJQwfYk/UFecWVdRDU/BMCPUjXdX1XbGeoVzhvjZdFrpkTo2ODLjemSgLeWq1wohfPP1fmZvuxEm+Dv4r2rc0kjkO11zvB0yZyPfdYIsMLrYPQgyCAlm805d3vv5995OPDfWXDiVsDnbX4NNGoJWAbIbT4rA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1731055117; c=relaxed/simple; bh=NIwDYhxDelSwnZl/GGCmkXrl0UAP3j9T0+ZJHuV/FUU=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=nv7smU8HfPcav47EyR0NP4n7qmKAhiQW8A5wMLeIguSCEjstIoDgVIYba47j1ek9cDWDjSFVYnUIBSRgbpZb2u4RuPU8Pz4pmClmZIEoefWAqH3Ye5tblCAL6aZMK55SnMEf+TfM3Mwmf+t8xac4ijZIBxi7MngOL7rBnZ9aF74= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=molgen.mpg.de; spf=pass smtp.mailfrom=molgen.mpg.de; arc=none smtp.client-ip=141.14.17.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=molgen.mpg.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=molgen.mpg.de Received: from [192.168.0.2] (unknown [95.90.242.139]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id BDE3A600AA639; Fri, 08 Nov 2024 09:37:44 +0100 (CET) Message-ID: <46444b60-2d1a-45c2-9a96-8352d1879516@molgen.mpg.de> Date: Fri, 8 Nov 2024 09:37:44 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v1] linux-firmware: update firmware for mediatek bluetooth chip (MT7920) To: Chris Lu Cc: Josh Boyer , David Woodhouse , Ben Hutchings , Marcel Holtmann , Johan Hedberg , Sean Wang , Allan Wang , Aaron Hou , Steve Lee , linux-bluetooth@vger.kernel.org, linux-firmware@kernel.org, linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org References: <20241108082515.19817-1-chris.lu@mediatek.com> Content-Language: en-US From: Paul Menzel In-Reply-To: <20241108082515.19817-1-chris.lu@mediatek.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 > --- > 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