From: Daniel Wagner <dwagner@suse.de>
To: linux-nvme@lists.infradead.org
Cc: Daniel Wagner <dwagner@suse.de>, Arthur Shau <arthurshau@fb.com>,
Wei Zhang <wzhang@fb.com>, Venkat Ramesh <venkatraghavan@fb.com>
Subject: [PATCH nvme-cli] ocp: Update license to GPL-2.0-or-later
Date: Tue, 17 May 2022 08:02:56 +0200 [thread overview]
Message-ID: <20220517060256.6733-1-dwagner@suse.de> (raw)
When I reviewed the plugin I asked wrongly for GPL-2.0-only. The
project is using the GPL-2.0-or-later license. Relax the license
requirement to GPL-2.0-or-later.
Cc: Arthur Shau <arthurshau@fb.com>
Cc: Wei Zhang <wzhang@fb.com>
Cc: Venkat Ramesh <venkatraghavan@fb.com>
Signed-off-by: Daniel Wagner <dwagner@suse.de>
---
Hi,
Could I get a signed-off-by for this?
Thanks!
Daniel
plugins/ocp/ocp-nvme.c | 2 +-
plugins/ocp/ocp-nvme.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/plugins/ocp/ocp-nvme.c b/plugins/ocp/ocp-nvme.c
index 1e7649b7d600..56cfdff9825f 100644
--- a/plugins/ocp/ocp-nvme.c
+++ b/plugins/ocp/ocp-nvme.c
@@ -1,4 +1,4 @@
-// SPDX-License-Identifier: GPL-2.0-only
+// SPDX-License-Identifier: GPL-2.0-or-later
/* Copyright (c) 2022 Meta Platforms, Inc.
*
* Authors: Arthur Shau <arthurshau@fb.com>,
diff --git a/plugins/ocp/ocp-nvme.h b/plugins/ocp/ocp-nvme.h
index 19378cdfcfdb..3e3f437aeaaf 100644
--- a/plugins/ocp/ocp-nvme.h
+++ b/plugins/ocp/ocp-nvme.h
@@ -1,4 +1,4 @@
-/* SPDX-License-Identifier: GPL-2.0-only */
+/* SPDX-License-Identifier: GPL-2.0-or-later */
/* Copyright (c) 2022 Meta Platforms, Inc.
*
* Authors: Arthur Shau <arthurshau@fb.com>,
--
2.36.0
next reply other threads:[~2022-05-17 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 6:02 Daniel Wagner [this message]
[not found] ` <DM6PR15MB290789265C9D82CC90216BD0B6CE9@DM6PR15MB2907.namprd15.prod.outlook.com>
2022-05-18 6:48 ` [PATCH nvme-cli] ocp: Update license to GPL-2.0-or-later Daniel Wagner
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=20220517060256.6733-1-dwagner@suse.de \
--to=dwagner@suse.de \
--cc=arthurshau@fb.com \
--cc=linux-nvme@lists.infradead.org \
--cc=venkatraghavan@fb.com \
--cc=wzhang@fb.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