Commit 081023a3 authored by Daniel Borkmann's avatar Daniel Borkmann

Merge branch 'bpf-formatting-fixes-helpers'

Quentin Monnet says:

====================
Here is a follow-up set for eBPF helper documentation, with two patches
to fix formatting issues:

- One to fix an error I introduced with the initial set for the doc.
- One for the newly added bpf_get_stack(), that is currently not parsed
  correctly with the Python script (function signature is fine, but
  description and return value appear as empty).

There is no change to text contents in this set.
====================
Signed-off-by: default avatarDaniel Borkmann <daniel@iogearbox.net>
parents 4d220ed0 a56497d3
...@@ -828,12 +828,12 @@ union bpf_attr { ...@@ -828,12 +828,12 @@ union bpf_attr {
* *
* Also, be aware that the newer helper * Also, be aware that the newer helper
* **bpf_perf_event_read_value**\ () is recommended over * **bpf_perf_event_read_value**\ () is recommended over
* **bpf_perf_event_read*\ () in general. The latter has some ABI * **bpf_perf_event_read**\ () in general. The latter has some ABI
* quirks where error and counter value are used as a return code * quirks where error and counter value are used as a return code
* (which is wrong to do since ranges may overlap). This issue is * (which is wrong to do since ranges may overlap). This issue is
* fixed with bpf_perf_event_read_value(), which at the same time * fixed with **bpf_perf_event_read_value**\ (), which at the same
* provides more features over the **bpf_perf_event_read**\ () * time provides more features over the **bpf_perf_event_read**\
* interface. Please refer to the description of * () interface. Please refer to the description of
* **bpf_perf_event_read_value**\ () for details. * **bpf_perf_event_read_value**\ () for details.
* Return * Return
* The value of the perf event counter read from the map, or a * The value of the perf event counter read from the map, or a
......
...@@ -828,12 +828,12 @@ union bpf_attr { ...@@ -828,12 +828,12 @@ union bpf_attr {
* *
* Also, be aware that the newer helper * Also, be aware that the newer helper
* **bpf_perf_event_read_value**\ () is recommended over * **bpf_perf_event_read_value**\ () is recommended over
* **bpf_perf_event_read*\ () in general. The latter has some ABI * **bpf_perf_event_read**\ () in general. The latter has some ABI
* quirks where error and counter value are used as a return code * quirks where error and counter value are used as a return code
* (which is wrong to do since ranges may overlap). This issue is * (which is wrong to do since ranges may overlap). This issue is
* fixed with bpf_perf_event_read_value(), which at the same time * fixed with **bpf_perf_event_read_value**\ (), which at the same
* provides more features over the **bpf_perf_event_read**\ () * time provides more features over the **bpf_perf_event_read**\
* interface. Please refer to the description of * () interface. Please refer to the description of
* **bpf_perf_event_read_value**\ () for details. * **bpf_perf_event_read_value**\ () for details.
* Return * Return
* The value of the perf event counter read from the map, or a * The value of the perf event counter read from the map, or a
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment