All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
To: Renjiang Han <renjiang.han@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: linux-firmware@kernel.org,
	"Qiwei Liu (QUIC)" <quic_qiweil@quicinc.com>,
	Wangao Wang <wangao.wang@oss.qualcomm.com>,
	dikshita.agarwal@oss.qualcomm.com
Subject: Re: update firmware binary for v5.4
Date: Fri, 21 Nov 2025 15:17:24 +0530	[thread overview]
Message-ID: <2b7be357-3a11-4eb7-ab6d-fb58c7909b07@oss.qualcomm.com> (raw)
In-Reply-To: <fa44f063-0f12-473a-98b1-cc601b4fade3@oss.qualcomm.com>


On 11/21/2025 9:27 AM, Renjiang Han wrote:
> 
> Hi Dmitry & Vikash
> 
> I have re-submitted two changes, please help check. Thanks!
> 
> 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
> 
>   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

It was made quite clear to put up the history from versions #58 all the 
way to #62 in the commit message, still i see commit message does not 
capture it.

Regards,
Vikash

  reply	other threads:[~2025-11-21  9:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19  9:39 update firmware binary for v5.4 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 [this message]
2025-11-21 11:55             ` Dmitry Baryshkov
2025-12-09  2:18               ` Renjiang Han
  -- strict thread matches above, loose matches on Subject: below --
2025-11-21  4:11 Renjiang Han
2025-11-23 14:11 ` Dmitry Baryshkov
2025-11-24  2:15   ` 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=2b7be357-3a11-4eb7-ab6d-fb58c7909b07@oss.qualcomm.com \
    --to=vikash.garodia@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=renjiang.han@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.