projects / linux-2.6-block.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 1d38226) | patch
bpf, libbpf: clarify bump in libbpf version info
authorDaniel Borkmann <daniel@iogearbox.net>
Sat, 23 Mar 2019 00:49:11 +0000 (01:49 +0100)
committerAlexei Starovoitov <ast@kernel.org>
Mon, 25 Mar 2019 02:49:04 +0000 (19:49 -0700)
commit63197f78bca2d86093126783b0ee6519bd652435
tree2cdc2befa846f45d2df230a322827a1b5c377b54tree | snapshot
parent1d382264d911d91a8be5dbed1f0e053eb3245d81commit | diff
bpf, libbpf: clarify bump in libbpf version info

The current documentation suggests that we would need to bump the
libbpf version on every change. Lets clarify this a bit more and
reflect what we do today in practice, that is, bumping it once per
development cycle.

Fixes: 76d1b894c515 ("libbpf: Document API and ABI conventions")
Reported-by: Stanislav Fomichev <sdf@google.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
tools/lib/bpf/README.rst diff | blob | blame | history
Linux 6.x block layer and io_uring tree(s)