projects
/
linux-2.6-microblaze.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
780d3d5
)
bpf, docs: Fix the code formatting in instruction-set
author
Shahab Vahedi
<Shahab.Vahedi@synopsys.com>
Fri, 24 Jun 2022 14:14:11 +0000
(14:14 +0000)
committer
Andrii Nakryiko
<andrii@kernel.org>
Fri, 24 Jun 2022 20:58:32 +0000
(13:58 -0700)
A minor typo fix to include "| BPF_LD" into its previous
code phrase:
``BPF_IND`` | BPF_LD --> ``BPF_IND | BPF_LD``
Signed-off-by: Shahab Vahedi <shahab@synopsys.com>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Link:
https://lore.kernel.org/bpf/b6120b31-3d1d-bf2d-2f2a-aa768d91257b@synopsys.com
Documentation/bpf/instruction-set.rst
patch
|
blob
|
history
diff --git
a/Documentation/bpf/instruction-set.rst
b/Documentation/bpf/instruction-set.rst
index
9e27fbd
..
1b0e671
100644
(file)
--- a/
Documentation/bpf/instruction-set.rst
+++ b/
Documentation/bpf/instruction-set.rst
@@
-351,7
+351,7
@@
These instructions have seven implicit operands:
* Register R0 is an implicit output which contains the data fetched from
the packet.
* Registers R1-R5 are scratch registers that are clobbered after a call to
- ``BPF_ABS | BPF_LD`` or ``BPF_IND
`` | BPF_LD
instructions.
+ ``BPF_ABS | BPF_LD`` or ``BPF_IND
| BPF_LD``
instructions.
These instructions have an implicit program exit condition as well. When an
eBPF program is trying to access the data beyond the packet boundary, the