From: Daniel Borkmann Date: Sat, 23 Mar 2019 00:49:11 +0000 (+0100) Subject: bpf, libbpf: clarify bump in libbpf version info X-Git-Tag: v5.1-rc3~35^2~12^2^2 X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=63197f78bca2d86093126783b0ee6519bd652435;p=users%2Fhch%2Fmisc.git 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 Signed-off-by: Daniel Borkmann Signed-off-by: Alexei Starovoitov --- diff --git a/tools/lib/bpf/README.rst b/tools/lib/bpf/README.rst index 5788479384ca..cef7b77eab69 100644 --- a/tools/lib/bpf/README.rst +++ b/tools/lib/bpf/README.rst @@ -111,6 +111,7 @@ starting from ``0.0.1``. Every time ABI is being changed, e.g. because a new symbol is added or semantic of existing symbol is changed, ABI version should be bumped. +This bump in ABI version is at most once per kernel development cycle. For example, if current state of ``libbpf.map`` is: