From: Guenter Roeck <linux@roeck-us.net>
To: SeongJae Park <sj@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/8] Docs/hwmon/index: Add missing SPDX License Identifier
Date: Mon, 30 Jan 2023 19:44:04 -0800 [thread overview]
Message-ID: <20230131034404.GA837158@roeck-us.net> (raw)
In-Reply-To: <20230122213650.187710-5-sj@kernel.org>
On Sun, Jan 22, 2023 at 09:36:46PM +0000, SeongJae Park wrote:
> Add missing SPDX License Identifier for hwmon documentation index file.
>
I do not feel comfortable accepting this change without confirmation
that changing the license from <none> to an explicit <GPL v2.0> is
legally acceptable.
Guenter
> Signed-off-by: SeongJae Park <sj@kernel.org>
> ---
> Documentation/hwmon/index.rst | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/hwmon/index.rst b/Documentation/hwmon/index.rst
> index c2b3c1a822dd..2186d732654f 100644
> --- a/Documentation/hwmon/index.rst
> +++ b/Documentation/hwmon/index.rst
> @@ -1,3 +1,5 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> ===================
> Hardware Monitoring
> ===================
next prev parent reply other threads:[~2023-01-31 3:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 21:36 [PATCH v2 0/8] Docs: Add missing SPDX license identifiers of SeongJae Park
2023-01-22 21:36 ` [PATCH v2 4/8] Docs/hwmon/index: Add missing SPDX License Identifier SeongJae Park
2023-01-24 13:49 ` Guenter Roeck
2023-01-31 3:44 ` Guenter Roeck [this message]
2023-01-31 14:44 ` Jonathan Corbet
2023-01-31 14:51 ` Mauro Carvalho Chehab
2023-01-31 14:48 ` Mauro Carvalho Chehab
2023-01-31 15:02 ` Guenter Roeck
2023-01-23 15:02 ` [PATCH v2 0/8] Docs: Add missing SPDX license identifiers of Jonathan Corbet
2023-01-24 22:31 ` Jonathan Corbet
2023-01-24 23:03 ` SeongJae Park
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=20230131034404.GA837158@roeck-us.net \
--to=linux@roeck-us.net \
--cc=corbet@lwn.net \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj@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).