diff options
| author | Daniel Borkmann <daniel@iogearbox.net> | 2019-01-07 22:57:18 +0100 |
|---|---|---|
| committer | Alexei Starovoitov <ast@kernel.org> | 2019-01-07 15:52:00 -0800 |
| commit | 80f21ff987eb377140d27102285f8dd1167b335c (patch) | |
| tree | c285c4764bb1c33787412c575c1f5dacf693ffea /tools | |
| parent | a769fa7208b94f37b6240215dc6970f9d76fc58c (diff) | |
bpf, doc: add note for libbpf's stand-alone build
Given this came up couple of times, add a note to libbpf's readme
about the semi-automated mirror for a stand-alone build which is
officially managed by BPF folks. While at it, also explicitly state
the libbpf license in the readme file.
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Acked-by: Alexei Starovoitov <ast@kernel.org>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'tools')
| -rw-r--r-- | tools/lib/bpf/README.rst | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/tools/lib/bpf/README.rst b/tools/lib/bpf/README.rst index 056f38310722..607aae40f4ed 100644 --- a/tools/lib/bpf/README.rst +++ b/tools/lib/bpf/README.rst @@ -132,6 +132,20 @@ For example, if current state of ``libbpf.map`` is: Format of version script and ways to handle ABI changes, including incompatible ones, described in details in [1]. +Stand-alone build +================= + +Under https://github.com/libbpf/libbpf there is a (semi-)automated +mirror of the mainline's version of libbpf for a stand-alone build. + +However, all changes to libbpf's code base must be upstreamed through +the mainline kernel tree. + +License +======= + +libbpf is dual-licensed under LGPL 2.1 and BSD 2-Clause. + Links ===== |