linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Dhaval Shah <dhaval23031987@gmail.com>,
	hyun.kwon@xilinx.com, laurent.pinchart@ideasonboard.com,
	michal.simek@xilinx.com, linux-media@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: v4l: xilinx: Use SPDX-License-Identifier
Date: Thu, 14 Dec 2017 15:35:43 -0200	[thread overview]
Message-ID: <20171214153543.598ca985@vento.lan> (raw)
In-Reply-To: <1513272387.27409.69.camel@perches.com>

Em Thu, 14 Dec 2017 09:26:27 -0800
Joe Perches <joe@perches.com> escreveu:

> On Thu, 2017-12-14 at 15:05 -0200, Mauro Carvalho Chehab wrote:
> > Em Fri,  8 Dec 2017 18:05:37 +0530
> > Dhaval Shah <dhaval23031987@gmail.com> escreveu:
> >   
> > > SPDX-License-Identifier is used for the Xilinx Video IP and
> > > related drivers.
> > > 
> > > Signed-off-by: Dhaval Shah <dhaval23031987@gmail.com>  
> > 
> > Hi Dhaval,
> > 
> > You're not listed as one of the Xilinx driver maintainers. I'm afraid that,
> > without their explicit acks, sent to the ML, I can't accept a patch
> > touching at the driver's license tags.  
> 
> And even a maintainer may not have the sole right
> to modify a license.

Very true. I was actually expecting a patch like that either authored
or explicitly sanctioned by either one of those developers:

Hyun Kwon <hyun.kwon@xilinx.com> (supporter:XILINX VIDEO IP CORES)
Michal Simek <michal.simek@xilinx.com> (supporter:ARM/ZYNQ ARCHITECTURE)

As they own an @xilinx.com, we could assume that an email from
their corporate accounts to be official.

Thanks,
Mauro

  reply	other threads:[~2017-12-14 17:35 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
2017-12-14 17:05 ` Mauro Carvalho Chehab
2017-12-14 17:26   ` Joe Perches
2017-12-14 17:35     ` Mauro Carvalho Chehab [this message]
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=20171214153543.598ca985@vento.lan \
    --to=mchehab@kernel.org \
    --cc=dhaval23031987@gmail.com \
    --cc=hyun.kwon@xilinx.com \
    --cc=joe@perches.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=michal.simek@xilinx.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).