From: Alexandre Courbot <acourbot@chromium.org>
To: gtk_ruiwang <gtk_ruiwang@mediatek.com>
Cc: linux-firmware@kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
srv_heupstream@mediatek.com, 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>
Subject: Re: [PATCH] mediatek: move MT8173 VPU FW to subfolder
Date: Wed, 26 Feb 2020 12:41:58 +0900 [thread overview]
Message-ID: <CAPBb6MWN6bXfYvpBJ6XyPCuvJSpdxNOf4Z9RbY0jbnB5=JX_sQ@mail.gmail.com> (raw)
Message-ID: <20200226034158.gmrC1gHfEoS-2bj8p_7JUDg5VxsFM40ewXHgPenEdJI@z> (raw)
In-Reply-To: <20200226033646.20949-2-gtk_ruiwang@mediatek.com>
On Wed, Feb 26, 2020 at 12:38 PM <gtk_ruiwang@mediatek.com> wrote:
>
> 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%)
This is nice as it removes some stuff from the root, but for
compatibility with older kernels that don't know about the new path
shouldn't we at least temporarily create a symbolic link between the
old location and the new one?
next prev parent reply other threads:[~2020-02-26 3:42 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 ` [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:36 ` gtk_ruiwang
2020-02-26 3:41 ` Alexandre Courbot [this message]
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='CAPBb6MWN6bXfYvpBJ6XyPCuvJSpdxNOf4Z9RbY0jbnB5=JX_sQ@mail.gmail.com' \
--to=acourbot@chromium.org \
--cc=PoChun.Lin@mediatek.com \
--cc=gtk_ruiwang@mediatek.com \
--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).