diff options
| author | Daniel Borkmann <daniel@iogearbox.net> | 2019-03-23 01:49:11 +0100 |
|---|---|---|
| committer | Alexei Starovoitov <ast@kernel.org> | 2019-03-24 19:49:04 -0700 |
| commit | 63197f78bca2d86093126783b0ee6519bd652435 (patch) | |
| tree | 2cdc2befa846f45d2df230a322827a1b5c377b54 | |
| parent | 1d382264d911d91a8be5dbed1f0e053eb3245d81 (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>
| -rw-r--r-- | tools/lib/bpf/README.rst | 1 |
1 files changed, 1 insertions, 0 deletions
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: |