linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] staging: sm750fb: add SPDX license identifier
Date: Mon, 14 May 2018 12:00:28 +0000	[thread overview]
Message-ID: <20180514120028.GA9139@kroah.com> (raw)
In-Reply-To: <20180508185102.GA21793@ubuntu>

On Sat, May 12, 2018 at 03:37:12AM +0530, Sumit Kumar wrote:
> 
> 
> On Friday 11 May 2018 03:13 PM, Greg Kroah-Hartman wrote:
> > On Wed, May 09, 2018 at 12:21:02AM +0530, Sumit Kumar wrote:
> > > SPDX licencse identifier is missing in header file. Add a SPDX license
> > > identifier with correct format. Issue found by checkpatch.
> > > 
> > > Signed-off-by: Sumit Kumar <sumit686215@example.com>
> > > ---
> > >   drivers/staging/sm750fb/ddk750.h | 1 +
> > >   1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/drivers/staging/sm750fb/ddk750.h b/drivers/staging/sm750fb/ddk750.h
> > > index 7340103..482c1c6 100644
> > > --- a/drivers/staging/sm750fb/ddk750.h
> > > +++ b/drivers/staging/sm750fb/ddk750.h
> > > @@ -1,3 +1,4 @@
> > > +/* SPDX-License-Identifier: GPL-2.0 */
> > How do you know that is what this license is?
> > 
> > thanks,
> > 
> > greg k-h
> 
> ddk750_chip.h had this license : /* SPDX-License-Identifier: GPL-2.0 */
> So I thought that maybe this header should also have the same license.

You need a bit more background information here in order to make this
decision in the patch.  Please see other patches that have added
licenses to files without them for what is needed.

thanks,

greg k-h

      parent reply	other threads:[~2018-05-14 12:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 18:53 [PATCH] staging: sm750fb: add SPDX license identifier Sumit Kumar
2018-05-11  9:43 ` Greg Kroah-Hartman
2018-05-11 22:19 ` Sumit Kumar
2018-05-14 12:00 ` Greg Kroah-Hartman [this message]

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=20180514120028.GA9139@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@vger.kernel.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).