linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Himanshu Jha <himanshujha199640@gmail.com>
To: jic23@kernel.org
Cc: linux-iio@vger.kernel.org,
	Daniel Baluta <daniel.baluta@gmail.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	linux-spdx@vger.kernel.org
Subject: Re: [PATCH 13/14] iio: trig-loop: SPDX headers GPL-v2
Date: Wed, 17 Jul 2019 23:28:37 +0530	[thread overview]
Message-ID: <20190717175837.GA31268@himanshu-Vostro-3559> (raw)
In-Reply-To: <20190622145516.3231-14-jic23@kernel.org>

On Sat, Jun 22, 2019 at 03:55:15PM +0100, jic23@kernel.org wrote:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> 
> Not exactly standard license text, but clear in intent and it's
> my copyright anyway.
> 
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
>  drivers/iio/trigger/iio-trig-loop.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/iio/trigger/iio-trig-loop.c b/drivers/iio/trigger/iio-trig-loop.c
> index 9258d3cf149b..f0205a9e47d0 100644
> --- a/drivers/iio/trigger/iio-trig-loop.c
> +++ b/drivers/iio/trigger/iio-trig-loop.c
> @@ -1,8 +1,7 @@
> +// SPDX-License-Identifier: GPL-2.0

I think it should be:

	// SPDX-License-Identifier: GPL-2.0-only

https://spdx.org/licenses/
https://spdx.org/licenses/GPL-2.0-only.html

I don't know if `spdxcheck.py` points out about
such a mismatch.

Yes, documentation and sanity checkers needs to be updated.
https://lore.kernel.org/lkml/CAHk-=wipjStEwJj2_iWxBdVC4oV8rY5NjrRb1tmWLUa0VrS_Eg@mail.gmail.com/


>  /*
>   * Copyright 2016 Jonathan Cameron <jic23@kernel.org>
>   *
> - * Licensed under the GPL-2.
> - *
>   * Based on a mashup of the hrtimer trigger and continuous sampling proposal of
>   * Gregor Boirie <gregor.boirie@parrot.com>
>   *
> -- 
> 2.22.0
> 

-- 
Himanshu Jha
Undergraduate Student
Department of Electronics & Communication
Guru Tegh Bahadur Institute of Technology

       reply	other threads:[~2019-07-17 17:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190622145516.3231-1-jic23@kernel.org>
     [not found] ` <20190622145516.3231-14-jic23@kernel.org>
2019-07-17 17:58   ` Himanshu Jha [this message]
2019-07-17 21:12     ` [PATCH 13/14] iio: trig-loop: SPDX headers GPL-v2 Greg KH
2019-08-17 19:08       ` J Lovejoy
2019-08-17 20:38         ` Greg KH

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=20190717175837.GA31268@himanshu-Vostro-3559 \
    --to=himanshujha199640@gmail.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=daniel.baluta@gmail.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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).