linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dhaval23031987@gmail.com (Dhaval Shah)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] media: v4l: xilinx: Use SPDX-License-Identifier
Date: Tue, 12 Dec 2017 11:39:05 +0530	[thread overview]
Message-ID: <CAOymtfLjf57-Utc+=99xCE3FBGGjySAO6JM3TE=crZ3MZUfzzA@mail.gmail.com> (raw)
In-Reply-To: <1766939.Rkg4NBiJVp@avalon>

Hi Laurent Pinchart,

Thanks a lot for the review.

On Mon, Dec 11, 2017 at 7:17 PM, Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
>
> Hi Dhaval,
>
> Thank you for the patch.
>
> On Friday, 8 December 2017 14:35:37 EET Dhaval Shah wrote:
> > SPDX-License-Identifier is used for the Xilinx Video IP and
> > related drivers.
> >
> > Signed-off-by: Dhaval Shah <dhaval23031987@gmail.com>
> > ---
> >  drivers/media/platform/xilinx/xilinx-dma.c  | 5 +----
> >  drivers/media/platform/xilinx/xilinx-dma.h  | 5 +----
> >  drivers/media/platform/xilinx/xilinx-tpg.c  | 5 +----
> >  drivers/media/platform/xilinx/xilinx-vip.c  | 5 +----
> >  drivers/media/platform/xilinx/xilinx-vip.h  | 5 +----
> >  drivers/media/platform/xilinx/xilinx-vipp.c | 5 +----
> >  drivers/media/platform/xilinx/xilinx-vipp.h | 5 +----
> >  drivers/media/platform/xilinx/xilinx-vtc.c  | 5 +----
> >  drivers/media/platform/xilinx/xilinx-vtc.h  | 5 +----
>
> How about addressing drivers/media/platform/xilinx/Makefile, drivers/media/
> platform/xilinx/Kconfig and include/dt-bindings/media/xilinx-vip.h as well ?
> If you're fine with that I can make the change when applying, there's no need
> to resubmit the patch.

Sorry, I forgot to update in those files. Thanks for that. I am fine
with what you said. Please do that change as you said.
>
> --
> Regards,
>
> Laurent Pinchart
>

  reply	other threads:[~2017-12-12  6:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08 12:35 [PATCH] media: v4l: xilinx: Use SPDX-License-Identifier Dhaval Shah
2017-12-11 13:47 ` Laurent Pinchart
2017-12-12  6:09   ` Dhaval Shah [this message]
2017-12-14 17:05 ` Mauro Carvalho Chehab
2017-12-14 17:26   ` Joe Perches
2017-12-14 17:35     ` Mauro Carvalho Chehab
2017-12-14 18:28   ` Laurent Pinchart
2017-12-14 18:32     ` Joe Perches
2017-12-14 18:37       ` Laurent Pinchart
2017-12-14 18:54         ` Joe Perches
2017-12-14 19:05           ` Laurent Pinchart
2017-12-14 20:08             ` Greg KH
2017-12-14 20:44               ` Laurent Pinchart
2017-12-14 20:57                 ` Greg KH
2017-12-14 21:50                   ` Mauro Carvalho Chehab
2017-12-14 22:02                     ` Laurent Pinchart
2017-12-15  5:25                       ` Dhaval Shah
2017-12-15  9:27                         ` Mauro Carvalho Chehab
2017-12-18  7:32                           ` Michal Simek
2017-12-18  8:32                             ` Laurent Pinchart
2017-12-18  8:56                               ` Michal Simek
2018-01-08 12:30                             ` Michal Simek
2017-12-15  9:23                       ` Mauro Carvalho Chehab

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='CAOymtfLjf57-Utc+=99xCE3FBGGjySAO6JM3TE=crZ3MZUfzzA@mail.gmail.com' \
    --to=dhaval23031987@gmail.com \
    --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).