From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kent Gibson <warthog618@gmail.com>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
"Dmitry V. Levin" <ldv@altlinux.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [libgpiod][PATCH 6/6] core: add the kernel uapi header to the repository
Date: Thu, 28 Jan 2021 08:51:29 +0100 [thread overview]
Message-ID: <YBJtAeyNHMFVHQ3o@kroah.com> (raw)
In-Reply-To: <20210128032641.GA11655@sol>
On Thu, Jan 28, 2021 at 11:26:41AM +0800, Kent Gibson wrote:
> Bart and Dmitry: I submit that we are good to copy the headers into the
> repositories, but we should take a few steps just to make clear that we
> are in full compliance with the GPL v2.
>
> Firstly, we are distributing the headers under Section 1 (distribution)
> of the GPL, so we should keep the headers in a separate directory that
> contains its own COPYING file as well as the GPL v2 and Linux syscall note
> - unless they are already available elsewhere in the repo.
>
> The headers must be copied verbatim so as to not trigger Section 2
> (modification). And it is probably good to include in the commit
> comment what kernel version or commit they were drawn from so that can
> be easily confirmed.
>
> Section 3 still doesn't apply, as any resulting object code or
> executables are no more a derived work due to the availability of the
> header than they were previously. And I don't think anyone is claiming
> that the repo itself is a derived work - in this context it is just a
> distribution medium.
>
> The COPYING file, or equivalent, for the project should explicitly
> exclude any claim on the kernel header directory to make clear we are
> not trying to sublicense the headers as LGPL - which could breach
> Section 4.
>
> Other than those points, I don't see anywhere we may be in breach.
That looks good, you should also consider following the REUSE
specification:
https://reuse.software/
which recommends using a LICENSES/ directory for the different licenses
in your project and use SPDX lines at the top of your files to make
everything explicit. The `reuse lint` command line tool should give you
lots of hints on good things to fix up in this area.
Good luck!
greg k-h
prev parent reply other threads:[~2021-01-28 7:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 13:34 [libgpiod][PATCH 0/6] treewide: remove more cruft and Bartosz Golaszewski
2021-01-11 13:34 ` [libgpiod][PATCH 1/6] treewide: remove helpers for opening chips by name & number Bartosz Golaszewski
2021-01-11 13:34 ` [libgpiod][PATCH 2/6] treewide: simplify the active-low line property Bartosz Golaszewski
2021-01-11 13:34 ` [libgpiod][PATCH 3/6] treewide: rename BIAS_AS_IS to BIAS_NONE Bartosz Golaszewski
2021-01-11 14:31 ` Kent Gibson
2021-01-11 13:34 ` [libgpiod][PATCH 4/6] treewide: make drive settings an enum Bartosz Golaszewski
2021-01-11 14:39 ` Kent Gibson
2021-01-11 14:48 ` Bartosz Golaszewski
2021-01-11 13:34 ` [libgpiod][PATCH 5/6] bindings: cxx: line: reorder bias mapping entries Bartosz Golaszewski
2021-01-11 13:34 ` [libgpiod][PATCH 6/6] core: add the kernel uapi header to the repository Bartosz Golaszewski
2021-01-11 13:46 ` Andy Shevchenko
2021-01-11 14:06 ` Bartosz Golaszewski
2021-01-11 14:46 ` Andy Shevchenko
2021-01-11 15:15 ` Bartosz Golaszewski
2021-01-25 5:55 ` Kent Gibson
2021-01-25 10:54 ` Andy Shevchenko
2021-01-26 15:07 ` Bartosz Golaszewski
2021-01-26 17:11 ` Greg Kroah-Hartman
2021-01-26 19:08 ` Bartosz Golaszewski
2021-01-27 11:43 ` Greg Kroah-Hartman
2021-01-28 3:26 ` Kent Gibson
2021-01-28 7:51 ` Greg Kroah-Hartman [this message]
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=YBJtAeyNHMFVHQ3o@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=ldv@altlinux.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=warthog618@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.