All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Irenge Jules Bashizi <jbi.octave@gmail.com>,
	mchehab@kernel.org, outreachy-kernel@googlegroups.com,
	jules.octave@outlook.com
Subject: Re: [Outreachy kernel] [PATCH] staging:dm365_ipipe:Add SPDX License Identifier
Date: Sat, 3 Nov 2018 16:06:55 +0100	[thread overview]
Message-ID: <20181103150655.GA3486@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1811031516160.2416@hadrien>

On Sat, Nov 03, 2018 at 03:16:39PM +0100, Julia Lawall wrote:
> 
> 
> On Sat, 3 Nov 2018, Irenge Jules Bashizi wrote:
> 
> > Add SPDX license Identifier to fix checkpatch malformed license warning
> >
> > Remove old style text describing the License
> >
> > Signed-off-by: Irenge Jules Bashizi <jbi.octave@gmail.com>
> > ---
> >  .../staging/media/davinci_vpfe/dm365_ipipe.c  | 31 ++++++-------------
> >  1 file changed, 9 insertions(+), 22 deletions(-)
> >
> > diff --git a/drivers/staging/media/davinci_vpfe/dm365_ipipe.c b/drivers/staging/media/davinci_vpfe/dm365_ipipe.c
> > index dcfeac818451..20bd6d652931 100644
> > --- a/drivers/staging/media/davinci_vpfe/dm365_ipipe.c
> > +++ b/drivers/staging/media/davinci_vpfe/dm365_ipipe.c
> > @@ -1,29 +1,16 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +
> >  /*
> > - * Copyright (C) 2012 Texas Instruments Inc
> 
> Is it correct to remove this?

Not at all, this should never be removed.

thanks,

greg k-h


  reply	other threads:[~2018-11-03 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-03 12:01 [PATCH] staging:dm365_ipipe:Add SPDX License Identifier Irenge Jules Bashizi
2018-11-03 14:12 ` [Outreachy kernel] " Julia Lawall
2018-11-03 14:16 ` Julia Lawall
2018-11-03 15:06   ` Greg KH [this message]
2018-11-03 22:25     ` Jules Octave

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=20181103150655.GA3486@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jbi.octave@gmail.com \
    --cc=jules.octave@outlook.com \
    --cc=julia.lawall@lip6.fr \
    --cc=mchehab@kernel.org \
    --cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.