From: Jonathan Corbet <corbet@lwn.net>
To: Guenter Roeck <linux@roeck-us.net>, SeongJae Park <sj@kernel.org>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH v2 4/8] Docs/hwmon/index: Add missing SPDX License Identifier
Date: Tue, 31 Jan 2023 07:44:02 -0700 [thread overview]
Message-ID: <87k0124vd9.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230131034404.GA837158@roeck-us.net>
Guenter Roeck <linux@roeck-us.net> writes:
> 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.
As with many of these, this file was initially added by Mauro (added to
CC). Mauro, can you confirm that GPLv2 was your intention for these
index.rst files? That would clear the path for a lot of these patches.
Thanks,
jon
next prev parent reply other threads:[~2023-01-31 14: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
2023-01-31 14:44 ` Jonathan Corbet [this message]
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=87k0124vd9.fsf@meer.lwn.net \
--to=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=linux@roeck-us.net \
--cc=mchehab@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).