From: jwboyer@kernel.org (Josh Boyer)
To: linux-arm-kernel@lists.infradead.org
Subject: pull request: linux-firmware: Update Mediatek MT8173 VPU firmware
Date: Fri, 19 Jan 2018 07:11:19 -0500 [thread overview]
Message-ID: <CA+5PVA6np4ZCCxE6Qk9s7UpN3By-3g1sqSg90xrD7BVjKu8ubw@mail.gmail.com> (raw)
In-Reply-To: <1516196123-24327-1-git-send-email-pochun.lin@mediatek.com>
On Wed, Jan 17, 2018 at 8:35 AM, <pochun.lin@mediatek.com> wrote:
> The following changes since commit 65b1c68c63f974d72610db38dfae49861117cae2:
>
> wl18xx: update firmware file 8.9.0.0.76 (2018-01-04 10:06:01 -0500)
>
> are available in the git repository at:
>
> https://github.com/pochun-lin/linux_fw_vpu_v1.0.8.git v1.0.8
>
> for you to fetch changes up to e72c23c9ff2ceeb3509cb6441cc81f0227edf06d:
>
> mediatek: update MT8173 VPU firmware to 1.0.8 (2018-01-17 20:19:56 +0800)
>
> ----------------------------------------------------------------
> pochun.lin (1):
> mediatek: update MT8173 VPU firmware to 1.0.8
Pulled and pushed out. If the firmware is versioned, perhaps that
version should be listed in the WHENCE file? You might want to add
that in a future patch.
josh
next prev parent reply other threads:[~2018-01-19 12:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 13:35 pull request: linux-firmware: Update Mediatek MT8173 VPU firmware pochun.lin at mediatek.com
2018-01-19 12:11 ` Josh Boyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-10 2:07 Irui Wang
2020-12-18 19:04 ` Josh Boyer
2020-02-18 10:03 gtk_ruiwang
2020-02-19 12:32 ` Josh Boyer
2020-01-14 9:18 gtk_ruiwang
2020-01-14 13:34 ` Josh Boyer
2019-04-02 2:05 Yunfei Dong
2019-04-02 11:58 ` Josh Boyer
2019-04-01 8:18 Yunfei Dong
2017-07-20 7:59 Andrew-CT Chen
2017-07-28 7:11 ` andrew-ct chen
2017-03-28 7:37 Andrew-CT Chen
2017-04-04 22:48 ` Kyle McMartin
2016-11-11 12:09 Andrew-CT Chen
2016-11-21 17:27 ` Kyle McMartin
2016-09-08 12:29 Andrew-CT Chen
2016-09-13 16:14 ` Kyle McMartin
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+5PVA6np4ZCCxE6Qk9s7UpN3By-3g1sqSg90xrD7BVjKu8ubw@mail.gmail.com \
--to=jwboyer@kernel.org \
--cc=linux-arm-kernel@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 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 NNTP newsgroup(s).