Re: [PATCH bpf-next] libbpf: relicense libbpf as LGPL-2.1 OR BSD-2-Clause

2 messages, 2 authors, 2018-10-08 · open the first message on its own page

Re: [PATCH bpf-next] libbpf: relicense libbpf as LGPL-2.1 OR BSD-2-Clause

From: Daniel Borkmann <daniel@iogearbox.net>
Date: 2018-10-08 08:15:36

On 10/05/2018 11:24 PM, Alexei Starovoitov wrote:
libbpf is maturing as a library and gaining features that no other bpf libraries support
(BPF Type Format, bpf to bpf calls, etc)
Many Apache2 licensed projects (like bcc, bpftrace, gobpf, cilium, etc)
would like to use libbpf, but cannot do this yet, since Apache Foundation explicitly
states that LGPL is incompatible with Apache2.
Hence let's relicense libbpf as dual license LGPL-2.1 or BSD-2-Clause,
since BSD-2 is compatible with Apache2.
Dual LGPL or Apache2 is invalid combination.
Fix license mistake in Makefile as well.

Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Acked-by: Andrey Ignatov <redacted>
Acked-by: Arnaldo Carvalho de Melo <acme@kernel.org>
Acked-by: Björn Töpel <redacted>
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
Acked-by: David Beckett <redacted>
Acked-by: Jakub Kicinski <redacted>
Acked-by: Joe Stringer <redacted>
Acked-by: John Fastabend <john.fastabend@gmail.com>
Acked-by: Martin KaFai Lau <redacted>
Acked-by: Quentin Monnet <redacted>
Acked-by: Thomas Graf <tgraf@suug.ch>
Acked-by: Roman Gushchin <redacted>
Acked-by: Wang Nan <redacted>
Acked-by: Yonghong Song <redacted>
Applied to bpf-next, thanks!

Re: [PATCH bpf-next] libbpf: relicense libbpf as LGPL-2.1 OR BSD-2-Clause

From: Jesper Dangaard Brouer <hidden>
Date: 2018-10-08 09:12:31

On Mon, 8 Oct 2018 10:15:10 +0200
Daniel Borkmann [off-list ref] wrote:
On 10/05/2018 11:24 PM, Alexei Starovoitov wrote:
quoted
libbpf is maturing as a library and gaining features that no other bpf libraries support
(BPF Type Format, bpf to bpf calls, etc)
Many Apache2 licensed projects (like bcc, bpftrace, gobpf, cilium, etc)
would like to use libbpf, but cannot do this yet, since Apache Foundation explicitly
states that LGPL is incompatible with Apache2.
Hence let's relicense libbpf as dual license LGPL-2.1 or BSD-2-Clause,
since BSD-2 is compatible with Apache2.
Dual LGPL or Apache2 is invalid combination.
Fix license mistake in Makefile as well.

Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Acked-by: Andrey Ignatov <redacted>
Acked-by: Arnaldo Carvalho de Melo <acme@kernel.org>
Acked-by: Björn Töpel <redacted>
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
Acked-by: David Beckett <redacted>
Acked-by: Jakub Kicinski <redacted>
Acked-by: Joe Stringer <redacted>
Acked-by: John Fastabend <john.fastabend@gmail.com>
Acked-by: Martin KaFai Lau <redacted>
Acked-by: Quentin Monnet <redacted>
Acked-by: Thomas Graf <tgraf@suug.ch>
Acked-by: Roman Gushchin <redacted>
Acked-by: Wang Nan <redacted>
Acked-by: Yonghong Song <redacted>  
Applied to bpf-next, thanks!
For the public record:
 Acked-by: Jesper Dangaard Brouer [off-list ref]

I do know, this ack will not reach the git-log, but given I have code
in the lib, I want to show that I support and ack this re-license.

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help