All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Kevin Hilman <khilman@baylibre.com>,
	Grant Likely <grant.likely@linaro.org>,
	linux-gpio@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Walter Lozano <walter.lozano@collabora.com>
Subject: Re: [libgpiod][PATCH 1/2] licensing: relicense C++ bindings under LGPL-2.1-or-later
Date: Wed, 17 Apr 2024 05:28:23 +0800	[thread overview]
Message-ID: <20240416212823.GA63139@rigel> (raw)
In-Reply-To: <20240416212141.6683-2-brgl@bgdev.pl>

On Tue, Apr 16, 2024 at 11:21:40PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> Commit ea84f882d5d3 ("licensing: relicense C++ library code under
> LGPL-3.0-or-later") changed the license of C++ bindings in order to
> solve potential issues with code generated from templates[1], default
> implementations, etc. However this change makes the bindings less
> attractive to projects that have strict licensing restrictions and avoid
> GPL-3.0 code[2].
>
> After talking to Grant Likely I decided that the best approach is to
> make the bindings available under LGPL-v2.1-or-later and simply let the
> end user decide which version's text to apply.
>
> While at it: tweak the README to also mention that examples are provided
> under GPL-2.0-or-later.
>
> Link: [1] https://www.spinics.net/lists/linux-gpio/msg46605.html
> Link: [2] https://github.com/brgl/libgpiod/issues/72
> Suggested-by: Walter Lozano <walter.lozano@collabora.com>
> Suggested-by: Grant Likely <grant.likely@linaro.org>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

Acked-by: Kent Gibson <warthog618@gmail.com>

  reply	other threads:[~2024-04-16 21:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 21:21 [libgpiod][PATCH 0/2] licensing: relicense C++ bindings and add a document on contributing Bartosz Golaszewski
2024-04-16 21:21 ` [libgpiod][PATCH 1/2] licensing: relicense C++ bindings under LGPL-2.1-or-later Bartosz Golaszewski
2024-04-16 21:28   ` Kent Gibson [this message]
2024-04-16 21:40   ` Kevin Hilman
2024-04-16 21:21 ` [libgpiod][PATCH 2/2] doc: add a file explaining the contribution process in detail Bartosz Golaszewski
2024-04-22 10:49 ` [libgpiod][PATCH 0/2] licensing: relicense C++ bindings and add a document on contributing Grant Likely
2024-04-22 12:06 ` Bartosz Golaszewski

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=20240416212823.GA63139@rigel \
    --to=warthog618@gmail.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=grant.likely@linaro.org \
    --cc=khilman@baylibre.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=walter.lozano@collabora.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.