linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: rt-users <linux-rt-users@vger.kernel.org>
Cc: Clark Williams <williams@redhat.com>, John Kacur <jkacur@redhat.com>
Subject: [PATCH 2/2] rt-tests: Add SPDX tag to hackbench.c
Date: Mon, 25 Nov 2019 23:38:10 +0100	[thread overview]
Message-ID: <20191125223810.16643-2-jkacur@redhat.com> (raw)
In-Reply-To: <20191125223810.16643-1-jkacur@redhat.com>

Add SPDX tag GPL-2.0-or-later
The original author is Rusty Russell

In his mail with the following message-id, he says:
Message-ID: <200911022357.36541.rusty@rustcorp.com.au>

> ( I've Cc:-ed Rusty, the original author of hackbench.c. Rusty, the file
>   has no explicit GPLv2 compatible license - is it fine to be put
>   into GPLv2 code? )

Yep, like all my code it's standard v2 "or later".

Sounds like a good plan, thanks!
Rusty.

Signed-off-by: John Kacur <jkacur@redhat.com>
---
 src/hackbench/hackbench.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/hackbench/hackbench.c b/src/hackbench/hackbench.c
index ba804f519950..5a883d341f2e 100644
--- a/src/hackbench/hackbench.c
+++ b/src/hackbench/hackbench.c
@@ -1,3 +1,4 @@
+// SPDX-License-Identifier: GPL-2.0-or-later
 /*
  * This is the latest version of hackbench.c, that tests scheduler and
  * unix-socket (or pipe) performance.
-- 
2.20.1


  reply	other threads:[~2019-11-25 22:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 22:38 [PATCH 1/2] rt-tests: Add SPDX tags V3 John Kacur
2019-11-25 22:38 ` John Kacur [this message]
2019-11-27 14:00   ` [PATCH 2/2] rt-tests: Add SPDX tag to hackbench.c Sebastian Andrzej Siewior

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=20191125223810.16643-2-jkacur@redhat.com \
    --to=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=williams@redhat.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).