From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Alexei Starovoitov <ast@kernel.org>,
davem@davemloft.net, acme@kernel.org, bjorn.topel@intel.com,
jakub.kicinski@netronome.com, tgraf@suug.ch, wangnan0@huawei.com,
colin.king@canonical.com, kraig@google.com,
daniel.diaz@linaro.org, eric@regit.org, hekuang@huawei.com,
jeremy@jcline.org, jolsa@kernel.org, joe@ovn.org,
yamada.masahiro@socionext.com, mic@digikod.net,
namhyung@kernel.org, ppenkov@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@fb.com,
brouer@redhat.com
Subject: Re: [PATCH bpf-next] libbpf: relicense libbpf as LGPL-2.1 OR BSD-2-Clause
Date: Mon, 8 Oct 2018 11:11:54 +0200 [thread overview]
Message-ID: <20181008111154.170c56dd@redhat.com> (raw)
In-Reply-To: <7a8a3ccd-d78f-8e3d-4759-34297e8e5357@iogearbox.net>
On Mon, 8 Oct 2018 10:15:10 +0200
Daniel Borkmann <daniel@iogearbox.net> wrote:
> 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 <rdna@fb.com>
> > Acked-by: Arnaldo Carvalho de Melo <acme@kernel.org>
> > Acked-by: Björn Töpel <bjorn.topel@intel.com>
> > Acked-by: Daniel Borkmann <daniel@iogearbox.net>
> > Acked-by: David Beckett <david.beckett@netronome.com>
> > Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
> > Acked-by: Joe Stringer <joe@ovn.org>
> > Acked-by: John Fastabend <john.fastabend@gmail.com>
> > Acked-by: Martin KaFai Lau <kafai@fb.com>
> > Acked-by: Quentin Monnet <quentin.monnet@netronome.com>
> > Acked-by: Thomas Graf <tgraf@suug.ch>
> > Acked-by: Roman Gushchin <guro@fb.com>
> > Acked-by: Wang Nan <wangnan0@huawei.com>
> > Acked-by: Yonghong Song <yhs@fb.com>
>
> Applied to bpf-next, thanks!
For the public record:
Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>
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
next prev parent reply other threads:[~2018-10-08 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181005212416.2525992-1-ast@kernel.org>
2018-10-08 8:15 ` [PATCH bpf-next] libbpf: relicense libbpf as LGPL-2.1 OR BSD-2-Clause Daniel Borkmann
2018-10-08 9:11 ` Jesper Dangaard Brouer [this message]
2018-10-05 23:40 Alexei Starovoitov
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=20181008111154.170c56dd@redhat.com \
--to=brouer@redhat.com \
--cc=acme@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=colin.king@canonical.com \
--cc=daniel.diaz@linaro.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eric@regit.org \
--cc=hekuang@huawei.com \
--cc=jakub.kicinski@netronome.com \
--cc=jeremy@jcline.org \
--cc=joe@ovn.org \
--cc=jolsa@kernel.org \
--cc=kernel-team@fb.com \
--cc=kraig@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mic@digikod.net \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ppenkov@google.com \
--cc=tgraf@suug.ch \
--cc=wangnan0@huawei.com \
--cc=yamada.masahiro@socionext.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 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).