mirror/libbpf
1
0
Fork 0
mirror of https://github.com/netdata/libbpf.git synced 2026-04-05 16:19:06 +08:00
Code Issues Packages Projects Releases Wiki Activity

libbpf, doc: Eliminate warnings in libbpf_naming_convention

Browse Source 
Use "code-block: none" instead of "c" for non-C-language code blocks.
Removes these warnings:

  lnx-514-rc4/Documentation/bpf/libbpf/libbpf_naming_convention.rst:111: WARNING: Could not lex literal_block as "c". Highlighting skipped.
  lnx-514-rc4/Documentation/bpf/libbpf/libbpf_naming_convention.rst:124: WARNING: Could not lex literal_block as "c". Highlighting skipped.

Fixes: f42cfb469f9b ("bpf: Add documentation for libbpf including API autogen")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Link: https://lore.kernel.org/bpf/20210802015037.787-1-rdunlap@infradead.org
This commit is contained in:
Randy Dunlap
2021-08-01 18:50:37 -07:00
committed by Andrii Nakryiko
parent 1a1e7a0612
commit c3f7daaab5
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/libbpf_naming_convention.rst
View File

@@ -108,7 +108,7 @@ This bump in ABI version is at most once per kernel development cycle.
For example, if current state of ``libbpf.map`` is: For example, if current state of ``libbpf.map`` is:
.. code-block:: c .. code-block:: none
LIBBPF_0.0.1 { LIBBPF_0.0.1 {
global: global:
@@ -121,7 +121,7 @@ For example, if current state of ``libbpf.map`` is:
, and a new symbol ``bpf_func_c`` is being introduced, then , and a new symbol ``bpf_func_c`` is being introduced, then
``libbpf.map`` should be changed like this: ``libbpf.map`` should be changed like this:
.. code-block:: c .. code-block:: none
LIBBPF_0.0.1 { LIBBPF_0.0.1 {
global: global: