From: <gtk_ruiwang@mediatek.com>
To: <linux-firmware@kernel.org>
Cc: <linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<srv_heupstream@mediatek.com>,
Alexandre Courbot <acourbot@chromium.org>,
Tomasz Figa <tfiga@chromium.org>, <PoChun.Lin@mediatek.com>,
Longfei Wang <longfei.wang@mediatek.com>,
Yunfei Dong <yunfei.dong@mediatek.com>,
Maoguang Meng <maoguang.meng@mediatek.com>,
<gtk_ruiwang@mediatek.com>
Subject: [PATCH] mediatek: move MT8173 VPU FW to subfolder
Date: Wed, 26 Feb 2020 11:36:46 +0800 [thread overview]
Message-ID: <20200226033646.20949-2-gtk_ruiwang@mediatek.com> (raw)
Message-ID: <20200226033646.P0gaCm5wpH1bdlcr41vJeM4YM8eOgLVtRLT4MlgnXX0@z> (raw)
In-Reply-To: <20200226033646.20949-1-gtk_ruiwang@mediatek.com>
From: gtk_ruiwang <gtk_ruiwang@mediatek.com>
Currently vpu_d.bin and vpu_p.bin are at the root of
linux-firmware git tree, it's not appropriate so we move
them to subfolder mediatek/mt8173
Release Version: 1.1.4
Signed-off-by: Rui Wang <gtk_ruiwang@mediatek.com>
---
vpu_d.bin => mediatek/mt8173/vpu_d.bin | Bin
vpu_p.bin => mediatek/mt8173/vpu_p.bin | Bin
2 files changed, 0 insertions(+), 0 deletions(-)
rename vpu_d.bin => mediatek/mt8173/vpu_d.bin (100%)
rename vpu_p.bin => mediatek/mt8173/vpu_p.bin (100%)
diff --git a/vpu_d.bin b/mediatek/mt8173/vpu_d.bin
similarity index 100%
rename from vpu_d.bin
rename to mediatek/mt8173/vpu_d.bin
diff --git a/vpu_p.bin b/mediatek/mt8173/vpu_p.bin
similarity index 100%
rename from vpu_p.bin
rename to mediatek/mt8173/vpu_p.bin
--
2.18.0
next prev parent reply other threads:[~2020-02-26 3:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 3:36 pull request: linux-firmware: move MT8173 VPU FW to subfolder gtk_ruiwang
2020-02-26 3:36 ` gtk_ruiwang
2020-02-26 3:36 ` gtk_ruiwang
2020-02-26 3:36 ` gtk_ruiwang
2020-02-26 3:36 ` gtk_ruiwang
2020-02-26 3:36 ` gtk_ruiwang [this message]
2020-02-26 3:36 ` [PATCH] mediatek: " gtk_ruiwang
2020-02-26 3:36 ` gtk_ruiwang
2020-02-26 3:36 ` gtk_ruiwang
2020-02-26 3:36 ` gtk_ruiwang
2020-02-26 3:41 ` Alexandre Courbot
2020-02-26 3:41 ` Alexandre Courbot
2020-02-26 3:41 ` Alexandre Courbot
2020-02-26 3:41 ` Alexandre Courbot
2020-02-26 3:41 ` Alexandre Courbot
2020-02-26 4:19 ` gtk_ruiwang
2020-02-26 4:19 ` gtk_ruiwang
2020-02-26 4:19 ` gtk_ruiwang
2020-02-26 4:19 ` gtk_ruiwang
2020-02-26 4:19 ` gtk_ruiwang
2020-02-26 4:45 ` Alexandre Courbot
2020-02-26 4:45 ` Alexandre Courbot
2020-02-26 4:45 ` Alexandre Courbot
2020-02-26 4:45 ` Alexandre Courbot
2020-02-26 4:45 ` Alexandre Courbot
2020-02-26 5:31 ` gtk_ruiwang
2020-02-26 5:31 ` gtk_ruiwang
2020-02-26 5:31 ` gtk_ruiwang
2020-02-26 5:31 ` gtk_ruiwang
2020-02-26 5:31 ` gtk_ruiwang
2020-02-26 5:26 pull request: linux-firmware: " gtk_ruiwang
2020-02-26 5:26 ` [PATCH] mediatek: " gtk_ruiwang
2020-02-26 5:26 ` gtk_ruiwang
2020-02-26 5:26 ` gtk_ruiwang
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=20200226033646.20949-2-gtk_ruiwang@mediatek.com \
--to=gtk_ruiwang@mediatek.com \
--cc=PoChun.Lin@mediatek.com \
--cc=acourbot@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=longfei.wang@mediatek.com \
--cc=maoguang.meng@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.org \
--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 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).