From: Renjiang Han <renjiang.han@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: linux-firmware@kernel.org,
"Qiwei Liu (QUIC)" <quic_qiweil@quicinc.com>,
Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
dikshita.agarwal@oss.qualcomm.com,
Wangao Wang <wangao.wang@oss.qualcomm.com>
Subject: Re: update firmware binary for v5.4
Date: Mon, 24 Nov 2025 10:15:35 +0800 [thread overview]
Message-ID: <7aff9b3c-64fe-4ddc-9345-191355e66133@oss.qualcomm.com> (raw)
In-Reply-To: <umzkvpxgwxjhaamdif4id3ngu2xrdvodyd64abc3obcrftccwg@dejqillpsk3q>
On 11/23/2025 10:11 PM, Dmitry Baryshkov wrote:
> On Fri, Nov 21, 2025 at 12:11:02PM +0800, Renjiang Han wrote:
>> Hi
>>
>> The following changes since commit 6fc940781a013ad837ed8fea326d2b897467bbc3:
>>
>> Merge branch 'robot/patch-0-1762826844' into 'main' (2025-11-11 12:02:02
>> +0000)
>>
>> are available in the Git repository at:
>>
>> https://git.codelinaro.org/clo/linux-kernel/linux-firmware.git
>> update-video-fw-v5.4
>>
>> for you to fetch changes up to bb28dcbcf9867ebeda6a41d575656a737c24f32f:
>>
>> qcom: venus-5.4: update firmware binary for v5.4 (2025-11-21 08:55:41
>> +0530)
>>
>> ----------------------------------------------------------------
>> Renjiang Han (2):
>> qcom: venus-5.4: remove unused firmware file
>> qcom: venus-5.4: update firmware binary for v5.4
> I've set to be merged, https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/793
>
> In future, please, write better explanations in commit messages. Target
> people who will read it in attempt to understand if it should be picked
> up for something like Debian stable rather than your close colleagues
> who perfectly know what the issue is.
>
> Also please coordinate your uploads with Vikash and Dikshita. The _s2
> suffix was totally not in line with other suffixes used beforehand or
> after.
Got it. Thanks!
>> WHENCE | 6 +-----
>> qcom/venus-5.4/venus.mbn | Bin 922216 -> 922312 bytes
>> qcom/venus-5.4/venus_s2.mbn | Bin 919008 -> 0 bytes
>> 3 files changed, 1 insertion(+), 5 deletions(-)
>> delete mode 100644 qcom/venus-5.4/venus_s2.mbn
>>
>> --
>> Best regards,
>> Renjiang Han
>>
--
Best regards,
Renjiang Han
next prev parent reply other threads:[~2025-11-24 2:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 4:11 update firmware binary for v5.4 Renjiang Han
2025-11-23 14:11 ` Dmitry Baryshkov
2025-11-24 2:15 ` Renjiang Han [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-19 9:39 Renjiang Han
2025-11-19 11:25 ` Dmitry Baryshkov
2025-11-19 14:27 ` Vikash Garodia
2025-11-19 14:52 ` Dmitry Baryshkov
2025-11-19 16:19 ` Vikash Garodia
2025-11-19 16:40 ` Dmitry Baryshkov
2025-11-19 17:13 ` Vikash Garodia
2025-11-20 1:03 ` Dmitry Baryshkov
2025-11-20 10:15 ` Vikash Garodia
2025-11-20 22:24 ` Dmitry Baryshkov
2025-11-21 8:07 ` Renjiang Han
2025-11-20 10:28 ` Renjiang Han
2025-11-21 2:50 ` Wangao Wang
2025-11-21 3:57 ` Renjiang Han
2025-11-21 9:47 ` Vikash Garodia
2025-11-21 11:55 ` Dmitry Baryshkov
2025-12-09 2:18 ` Renjiang Han
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=7aff9b3c-64fe-4ddc-9345-191355e66133@oss.qualcomm.com \
--to=renjiang.han@oss.qualcomm.com \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=linux-firmware@kernel.org \
--cc=quic_qiweil@quicinc.com \
--cc=vikash.garodia@oss.qualcomm.com \
--cc=wangao.wang@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.