* [PATCH bpf-next v1 1/1] docs: fixup cpumap sphinx >= 3.1 warning
@ 2022-11-13 10:33 mtahhan
2022-11-13 23:21 ` Akira Yokosawa
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: mtahhan @ 2022-11-13 10:33 UTC (permalink / raw)
To: bpf, linux-doc; +Cc: jbrouer, thoiland, donhunte, akiyks, Maryam Tahhan
From: Maryam Tahhan <mtahhan@redhat.com>
Fixup bpf_map_update_elem() declaration to use a single line.
Signed-off-by: Maryam Tahhan <mtahhan@redhat.com>
Reported-by: Akira Yokosawa <akiyks@gmail.com>
---
Documentation/bpf/map_cpumap.rst | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Documentation/bpf/map_cpumap.rst b/Documentation/bpf/map_cpumap.rst
index eaf57b38cafd..61a797a86342 100644
--- a/Documentation/bpf/map_cpumap.rst
+++ b/Documentation/bpf/map_cpumap.rst
@@ -48,8 +48,7 @@ Userspace
program will result in the program failing to load and a verifier warning.
.. c:function::
- int bpf_map_update_elem(int fd, const void *key, const void *value,
- __u64 flags);
+ int bpf_map_update_elem(int fd, const void *key, const void *value, __u64 flags);
CPU entries can be added or updated using the ``bpf_map_update_elem()``
helper. This helper replaces existing elements atomically. The ``value`` parameter
--
2.35.3
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH bpf-next v1 1/1] docs: fixup cpumap sphinx >= 3.1 warning
2022-11-13 10:33 [PATCH bpf-next v1 1/1] docs: fixup cpumap sphinx >= 3.1 warning mtahhan
@ 2022-11-13 23:21 ` Akira Yokosawa
2022-11-14 17:22 ` sdf
2022-11-14 18:20 ` patchwork-bot+netdevbpf
2 siblings, 0 replies; 4+ messages in thread
From: Akira Yokosawa @ 2022-11-13 23:21 UTC (permalink / raw)
To: mtahhan, bpf, linux-doc; +Cc: jbrouer, thoiland, donhunte, Akira Yokosawa
On Sun, 13 Nov 2022 05:33:27 -0500, mtahhan@redhat.com wrote:
> From: Maryam Tahhan <mtahhan@redhat.com>
>
> Fixup bpf_map_update_elem() declaration to use a single line.
>
> Signed-off-by: Maryam Tahhan <mtahhan@redhat.com>
> Reported-by: Akira Yokosawa <akiyks@gmail.com>
Tested-by: Akira Yokosawa <akiyks@gmail.com>
Thanks, Akira
> ---
> Documentation/bpf/map_cpumap.rst | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/Documentation/bpf/map_cpumap.rst b/Documentation/bpf/map_cpumap.rst
> index eaf57b38cafd..61a797a86342 100644
> --- a/Documentation/bpf/map_cpumap.rst
> +++ b/Documentation/bpf/map_cpumap.rst
> @@ -48,8 +48,7 @@ Userspace
> program will result in the program failing to load and a verifier warning.
>
> .. c:function::
> - int bpf_map_update_elem(int fd, const void *key, const void *value,
> - __u64 flags);
> + int bpf_map_update_elem(int fd, const void *key, const void *value, __u64 flags);
>
> CPU entries can be added or updated using the ``bpf_map_update_elem()``
> helper. This helper replaces existing elements atomically. The ``value`` parameter
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH bpf-next v1 1/1] docs: fixup cpumap sphinx >= 3.1 warning
2022-11-13 10:33 [PATCH bpf-next v1 1/1] docs: fixup cpumap sphinx >= 3.1 warning mtahhan
2022-11-13 23:21 ` Akira Yokosawa
@ 2022-11-14 17:22 ` sdf
2022-11-14 18:20 ` patchwork-bot+netdevbpf
2 siblings, 0 replies; 4+ messages in thread
From: sdf @ 2022-11-14 17:22 UTC (permalink / raw)
To: mtahhan; +Cc: bpf, linux-doc, jbrouer, thoiland, donhunte, akiyks
On 11/13, mtahhan@redhat.com wrote:
> From: Maryam Tahhan <mtahhan@redhat.com>
> Fixup bpf_map_update_elem() declaration to use a single line.
> Signed-off-by: Maryam Tahhan <mtahhan@redhat.com>
> Reported-by: Akira Yokosawa <akiyks@gmail.com>
Acked-by: Stanislav Fomichev <sdf@google.com>
> ---
> Documentation/bpf/map_cpumap.rst | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
> diff --git a/Documentation/bpf/map_cpumap.rst
> b/Documentation/bpf/map_cpumap.rst
> index eaf57b38cafd..61a797a86342 100644
> --- a/Documentation/bpf/map_cpumap.rst
> +++ b/Documentation/bpf/map_cpumap.rst
> @@ -48,8 +48,7 @@ Userspace
> program will result in the program failing to load and a verifier
> warning.
> .. c:function::
> - int bpf_map_update_elem(int fd, const void *key, const void *value,
> - __u64 flags);
> + int bpf_map_update_elem(int fd, const void *key, const void *value,
> __u64 flags);
> CPU entries can be added or updated using the ``bpf_map_update_elem()``
> helper. This helper replaces existing elements atomically. The
> ``value`` parameter
> --
> 2.35.3
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH bpf-next v1 1/1] docs: fixup cpumap sphinx >= 3.1 warning
2022-11-13 10:33 [PATCH bpf-next v1 1/1] docs: fixup cpumap sphinx >= 3.1 warning mtahhan
2022-11-13 23:21 ` Akira Yokosawa
2022-11-14 17:22 ` sdf
@ 2022-11-14 18:20 ` patchwork-bot+netdevbpf
2 siblings, 0 replies; 4+ messages in thread
From: patchwork-bot+netdevbpf @ 2022-11-14 18:20 UTC (permalink / raw)
To: Maryam Tahhan; +Cc: bpf, linux-doc, jbrouer, thoiland, donhunte, akiyks
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Sun, 13 Nov 2022 05:33:27 -0500 you wrote:
> From: Maryam Tahhan <mtahhan@redhat.com>
>
> Fixup bpf_map_update_elem() declaration to use a single line.
>
> Signed-off-by: Maryam Tahhan <mtahhan@redhat.com>
> Reported-by: Akira Yokosawa <akiyks@gmail.com>
>
> [...]
Here is the summary with links:
- [bpf-next,v1,1/1] docs: fixup cpumap sphinx >= 3.1 warning
https://git.kernel.org/bpf/bpf-next/c/e662c7753668
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-11-14 18:20 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-11-13 10:33 [PATCH bpf-next v1 1/1] docs: fixup cpumap sphinx >= 3.1 warning mtahhan
2022-11-13 23:21 ` Akira Yokosawa
2022-11-14 17:22 ` sdf
2022-11-14 18:20 ` patchwork-bot+netdevbpf
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).