From: Josh Boyer <jwboyer@kernel.org>
To: Irui Wang <irui.wang@mediatek.com>
Cc: linux-firmware@kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, Longfei.Wang@mediatek.com,
Yunfei.Dong@mediatek.com, Andrew-CT.Chen@mediatek.com,
tiffany.lin@mediatek.com,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: pull request: linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.9
Date: Wed, 10 Apr 2024 07:46:26 -0400 [thread overview]
Message-ID: <CA+5PVA5xfwVvLbKYNPKWJAqOw49VspoVnmHaZ0r2c4jBKNW85w@mail.gmail.com> (raw)
In-Reply-To: <20240410111416.2204-1-irui.wang@mediatek.com>
On Wed, Apr 10, 2024 at 7:14 AM Irui Wang <irui.wang@mediatek.com> wrote:
>
> Dear linux-firmware maintainers,
>
> The following changes since commit 1addd7dca2d953a5484c3e3c08dbd7dc253058dd:
>
> Merge branch 'rtw' into 'main' (2024-04-09 12:30:28 +0000)
>
> are available in the Git repository at:
>
> https://github.com/irui-wang/linux_fw_vpu_v1.1.9.git v1.1.9
Pulled and pushed out.
https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/191
josh
>
> for you to fetch changes up to c81f094c847d934c0ffe0870fa5cf861c62e3451:
>
> linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.9 (2024-04-10 18:36:10 +0800)
>
> ----------------------------------------------------------------
> Irui Wang (1):
> linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.9
>
> mediatek/mt8173/vpu_d.bin | Bin 2977184 -> 2977184 bytes
> mediatek/mt8173/vpu_p.bin | Bin 131380 -> 131380 bytes
> 2 files changed, 0 insertions(+), 0 deletions(-)
>
>
prev parent reply other threads:[~2024-04-10 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 11:14 pull request: linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.9 Irui Wang
2024-04-10 11:14 ` [PATCH] " Irui Wang
2024-04-10 11:46 ` Josh Boyer [this message]
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=CA+5PVA5xfwVvLbKYNPKWJAqOw49VspoVnmHaZ0r2c4jBKNW85w@mail.gmail.com \
--to=jwboyer@kernel.org \
--cc=Andrew-CT.Chen@mediatek.com \
--cc=Longfei.Wang@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Yunfei.Dong@mediatek.com \
--cc=irui.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-firmware@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=tiffany.lin@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).