[<prev] [next>] [day] [month] [year] [list]
Message-ID: <DB66473733449DB0+20250423030632.17626-1-wangyuli@uniontech.com>
Date: Wed, 23 Apr 2025 11:06:32 +0800
From: WangYuli <wangyuli@...ontech.com>
To: ast@...nel.org,
daniel@...earbox.net,
andrii@...nel.org,
martin.lau@...ux.dev,
eddyz87@...il.com,
song@...nel.org,
yonghong.song@...ux.dev,
john.fastabend@...il.com,
kpsingh@...nel.org,
sdf@...ichev.me,
haoluo@...gle.com,
jolsa@...nel.org,
corbet@....net
Cc: bpf@...r.kernel.org,
linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org,
void@...ifault.com,
psreep@...il.com,
yhs@...com,
zhanjun@...ontech.com,
niecheng1@...ontech.com,
guanwentao@...ontech.com,
WangYuli <wangyuli@...ontech.com>,
Chen Linxuan <chenlinxuan@...ontech.com>
Subject: [PATCH] bpf, docs: iterator: Rectify non-standard line break
Even though the kernel's coding-style document does not explicitly
state this, we generally put a newline after the semicolon of every
C language statement to enhance code readability.
Adjust the placement of newlines to adhere to this convention.
Reported-by: Chen Linxuan <chenlinxuan@...ontech.com>
Signed-off-by: WangYuli <wangyuli@...ontech.com>
---
Documentation/bpf/bpf_iterators.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/bpf/bpf_iterators.rst b/Documentation/bpf/bpf_iterators.rst
index 7f514cb6b052..385cd05aabf5 100644
--- a/Documentation/bpf/bpf_iterators.rst
+++ b/Documentation/bpf/bpf_iterators.rst
@@ -323,8 +323,8 @@ Now, in the userspace program, pass the pointer of struct to the
::
- link = bpf_program__attach_iter(prog, &opts); iter_fd =
- bpf_iter_create(bpf_link__fd(link));
+ link = bpf_program__attach_iter(prog, &opts);
+ iter_fd = bpf_iter_create(bpf_link__fd(link));
If both *tid* and *pid* are zero, an iterator created from this struct
``bpf_iter_attach_opts`` will include every opened file of every task in the
--
2.49.0
Powered by blists - more mailing lists