From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Nikhil Devshatwar <nikhil.nd@ti.com>
Cc: linux-firmware@kernel.org, linux-media@vger.kernel.org,
Dan Murphy <dmurphy@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Benoit Parrot <bparrot@ti.com>, Sekhar Nori <nsekhar@ti.com>
Subject: Re: [PATCH] vpdma: Move firmware to the toplevel
Date: Mon, 26 Oct 2020 23:08:32 +0200 [thread overview]
Message-ID: <20201026210832.GE3756@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20201026200922.12719-1-nikhil.nd@ti.com>
Hi Nikhil,
Thank you for the patch.
On Tue, Oct 27, 2020 at 01:39:22AM +0530, Nikhil Devshatwar wrote:
> Move the vpdma firmware to the toplevel directory so
> that the existing drivers can use it with the same path.
>
> Fixes: 5b30b383ce ("linux-firmware: Add new VPDMA firmware 1b8.bin")
> Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
> ---
> WHENCE | 2 +-
> ti-connectivity/vpdma-1b8.bin => vpdma-1b8.bin | Bin
I think Tomi meant moving the file to ti/ instead of ti-connectivity/. I
will let him comment on this.
> 2 files changed, 1 insertion(+), 1 deletion(-)
> rename ti-connectivity/vpdma-1b8.bin => vpdma-1b8.bin (100%)
>
> diff --git a/WHENCE b/WHENCE
> index 473f6fb..347593c 100644
> --- a/WHENCE
> +++ b/WHENCE
> @@ -2705,7 +2705,7 @@ Licence: Redistributable. See LICENCE.tda7706-firmware.txt for details.
>
> Driver: ti-vpe - Texas Instruments V4L2 driver for Video Processing Engine
>
> -File: ti-connectivity/vpdma-1b8.bin
> +File: vpdma-1b8.bin
>
> Licence: Redistributable. See LICENCE.ti-tspa for details.
>
> diff --git a/ti-connectivity/vpdma-1b8.bin b/vpdma-1b8.bin
> similarity index 100%
> rename from ti-connectivity/vpdma-1b8.bin
> rename to vpdma-1b8.bin
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2020-10-26 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 20:09 [PATCH] vpdma: Move firmware to the toplevel Nikhil Devshatwar
2020-10-26 21:08 ` Laurent Pinchart [this message]
2020-10-28 7:41 ` Tomi Valkeinen
2020-10-28 17:19 ` Nikhil Devshatwar
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=20201026210832.GE3756@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=bparrot@ti.com \
--cc=dmurphy@ti.com \
--cc=linux-firmware@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=nikhil.nd@ti.com \
--cc=nsekhar@ti.com \
--cc=tomi.valkeinen@ti.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