From: Josh Boyer <jwboyer@kernel.org>
To: Tinghan Shen <tinghan.shen@mediatek.com>
Cc: Linux Firmware <linux-firmware@kernel.org>,
linux-mediatek <linux-mediatek@lists.infradead.org>,
Yunfei Dong <yunfei.dong@mediatek.com>,
Shawn Ku <shawnku@google.com>,
Project_Global_Chrome_Upstream_Group@mediatek.com,
Justin.Yeh@mediatek.com,
"allen-kh.cheng" <Allen-KH.Cheng@mediatek.com>
Subject: Re: pull request: linux-firmware: Update Mediatek MT8183/MT8192/MT8195 SCP firmware
Date: Mon, 25 Jul 2022 14:15:46 -0400 [thread overview]
Message-ID: <CA+5PVA6uJtrzZZ=k0g6u1ycTm-oXSuuUoddSG8rUebGftnKu5g@mail.gmail.com> (raw)
In-Reply-To: <42437b6fc5dac19bf23f9806dfbe6915e055397b.camel@mediatek.com>
On Fri, Jul 22, 2022 at 4:29 AM Tinghan Shen <tinghan.shen@mediatek.com> wrote:
>
> Hi maintainers,
>
> Update SCP firmware for MediaTek MT8183/MT8192/MT8195.
> Thank you!
>
>
> Regards,
> TingHan
>
> ---
>
> The following changes since commit 4421586e8e95ce789cb6b3f1af98962bfef74c7b:
>
> amdgpu: update renoir to release 22.20 (2022-07-19 06:44:08 -0400)
>
> are available in the Git repository at:
>
> https://github.com/tinghan-shen/linux_fw_scp mtk-scp-20220722
>
> for you to fetch changes up to 56cf6461a82b08facd41154f7c44a19f0a085f66:
>
> mediatek: Update mt8183/mt8192/mt8195 SCP firmware (2022-07-22 16:16:27 +0800)
>
> ----------------------------------------------------------------
> Tinghan Shen (1):
> mediatek: Update mt8183/mt8192/mt8195 SCP firmware
Pulled and pushed out. Thanks.
josh
>
> WHENCE | 6 +++---
> mediatek/mt8183/scp.img | Bin 1032064 -> 1030776 bytes
> mediatek/mt8192/scp.img | Bin 327968 -> 328096 bytes
> mediatek/mt8195/scp.img | Bin 429668 -> 429820 bytes
> 4 files changed, 3 insertions(+), 3 deletions(-)
>
next prev parent reply other threads:[~2022-07-25 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 8:29 pull request: linux-firmware: Update Mediatek MT8183/MT8192/MT8195 SCP firmware Tinghan Shen
2022-07-25 18:15 ` Josh Boyer [this message]
2023-01-12 20:46 ` Nícolas F. R. A. Prado
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+5PVA6uJtrzZZ=k0g6u1ycTm-oXSuuUoddSG8rUebGftnKu5g@mail.gmail.com' \
--to=jwboyer@kernel.org \
--cc=Allen-KH.Cheng@mediatek.com \
--cc=Justin.Yeh@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=linux-firmware@kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=shawnku@google.com \
--cc=tinghan.shen@mediatek.com \
--cc=yunfei.dong@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 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.