From: Josh Boyer <jwboyer@kernel.org>
To: "Hailong Fan (范海龙)" <Hailong.Fan@mediatek.com>
Cc: "linux-firmware@kernel.org" <linux-firmware@kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PULL] mediatek: Update mt8186 SOF firmware to v2.0.1
Date: Fri, 22 Mar 2024 09:39:33 -0400 [thread overview]
Message-ID: <CA+5PVA5unmBTXbiksB=N5x16RinxnYGgevPYZ0Hd2j7owLGRsQ@mail.gmail.com> (raw)
In-Reply-To: <30f41011495fb0b11a11eef9c7a536268306edb2.camel@mediatek.com>
On Fri, Mar 22, 2024 at 5:32 AM Hailong Fan (范海龙)
<Hailong.Fan@mediatek.com> wrote:
>
> Hi maintainers,
>
> This pull request updates MT8186 SOF firmware.
>
> If there is any problem, please let me know.
> Thank you.
>
> Best regards,
> Hailong
>
> --
>
> The following changes since commit
> 22ee1d8ca6663ca7c28477581993d6ed5cc54323:
>
> Merge branch 'robot/pr-0-1710861164' into 'main' (2024-03-19 19:07:14
> +0000)
>
> are available in the Git repository at:
>
> https://github.com/hailongfan-mtk/linux_fw_sof v2.0.1
Merged and pushed out.
https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/183
josh
>
> for you to fetch changes up to
> 9a6a0cc195c108c677165075c55cbc0e417a1e64:
>
> mekdiatek: Update mt8186 SOF firmware to v2.0.1 (2024-03-22 17:04:27
> +0800)
>
> ----------------------------------------------------------------
> Hailong Fan (1):
> mekdiatek: Update mt8186 SOF firmware to v2.0.1
>
> mediatek/sof-tplg/sof-mt8186.tplg | Bin 16191 -> 16191 bytes
> mediatek/sof/sof-mt8186.ldc | Bin 48436 -> 48564 bytes
> mediatek/sof/sof-mt8186.ri | Bin 128712 -> 129304 bytes
> 3 files changed, 0 insertions(+), 0 deletions(-)
next prev parent reply other threads:[~2024-03-22 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 9:32 [PULL] mediatek: Update mt8186 SOF firmware to v2.0.1 Hailong Fan (范海龙)
2024-03-22 13:39 ` Josh Boyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-22 6:32 Hailong Fan (范海龙)
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+5PVA5unmBTXbiksB=N5x16RinxnYGgevPYZ0Hd2j7owLGRsQ@mail.gmail.com' \
--to=jwboyer@kernel.org \
--cc=Hailong.Fan@mediatek.com \
--cc=linux-firmware@kernel.org \
--cc=linux-mediatek@lists.infradead.org \
/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.