From: Tinghan Shen <tinghan.shen@mediatek.com>
To: Josh Boyer <jwboyer@kernel.org>
Cc: <linux-firmware@kernel.org>, <linux-mediatek@lists.infradead.org>,
<chunxu.li@mediatek.com>, <allen-kh.cheng@mediatek.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PULL linux-firmware] mediatek mt8186 SOF firmware v0.2.0
Date: Tue, 16 Aug 2022 09:43:16 +0800 [thread overview]
Message-ID: <ca48295d59f23b68ef48b303e8d3e065ac95378e.camel@mediatek.com> (raw)
In-Reply-To: <CA+5PVA5_tj63z8izA_wigVtXzCUDSbuAhgtpVS6psSBdSXJ1dg@mail.gmail.com>
On Mon, 2022-08-15 at 09:01 -0400, Josh Boyer wrote:
> On Mon, Aug 15, 2022 at 5:13 AM Tinghan Shen <tinghan.shen@mediatek.com> wrote:
> >
> > Hi maintainers,
> >
> > This pull request adds new MediatekTek firmware for MT8186 SOF.
> >
> > Please let me know if there are any problems.
> >
> > Best regards,
> > TingHan
> >
> > ---
> >
> > The following changes since commit ad5ae82019480dc1feffb538c118397a40934e62:
> >
> > Merge branch 'main' of
> > https://urldefense.com/v3/__https://github.com/suraj714/BT-Upstream__;!!CTRNKA9wMg0ARbw!1yTVOC7UDhMs-zna3kGo4Pq4k6mbowX_CHWQLh_iIdpK3fQ2bZEwZd0e2XNzAwQPNFc$
> > (2022-08-10 07:58:34 -0400)
> >
> > are available in the Git repository at:
> >
> >
> > https://urldefense.com/v3/__https://github.com/tinghan-shen/linux_fw_scp__;!!CTRNKA9wMg0ARbw!1yTVOC7UDhMs-zna3kGo4Pq4k6mbowX_CHWQLh_iIdpK3fQ2bZEwZd0e2XNzSAFZtnA$
> > mt8186-sof-20220815
> >
> > for you to fetch changes up to 12ca0753342651fa2ab640deffde5e51b0dd9868:
> >
> > mediatek: Add new mt8186 SOF firmware (2022-08-15 16:43:11 +0800)
> >
> > ----------------------------------------------------------------
> > Tinghan Shen (1):
> > mediatek: Add new mt8186 SOF firmware
> >
> > WHENCE | 21 +++++++++++++++++++++
>
> Pulled and pushed out.
>
> I noticed several of the Mediatek entries in WHENCE all put the
> license information in the WHENCE file, but LICENCE.mediatek also
> exists with the same terms. Can we clean up WHENCE and just have all
> the entries reference that file?
>
> josh
No problem. I hadn't noticed that file before.
I'll send another pull request to clean it.
Best regards,
TingHan
next prev parent reply other threads:[~2022-08-16 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 9:13 [PULL linux-firmware] mediatek mt8186 SOF firmware v0.2.0 Tinghan Shen
2022-08-15 13:01 ` Josh Boyer
2022-08-16 1:43 ` Tinghan Shen [this message]
2022-08-16 2:22 ` [PULL linux-firmware] Clean up mediatek WHENCE licence terms Tinghan Shen
2022-08-29 11:46 ` Josh Boyer
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=ca48295d59f23b68ef48b303e8d3e065ac95378e.camel@mediatek.com \
--to=tinghan.shen@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=chunxu.li@mediatek.com \
--cc=jwboyer@kernel.org \
--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.