BPF List
 help / color / mirror / Atom feed
From: sdf@google.com
To: mtahhan@redhat.com
Cc: bpf@vger.kernel.org, linux-doc@vger.kernel.org,
	jbrouer@redhat.com, thoiland@redhat.com, donhunte@redhat.com,
	akiyks@gmail.com
Subject: Re: [PATCH bpf-next v1 1/1] docs: fixup cpumap sphinx >= 3.1 warning
Date: Mon, 14 Nov 2022 09:22:22 -0800	[thread overview]
Message-ID: <Y3J5ThS9VGVVgsKf@google.com> (raw)
In-Reply-To: <20221113103327.3287482-1-mtahhan@redhat.com>

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


  parent reply	other threads:[~2022-11-14 17:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2022-11-14 18:20 ` patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y3J5ThS9VGVVgsKf@google.com \
    --to=sdf@google.com \
    --cc=akiyks@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=donhunte@redhat.com \
    --cc=jbrouer@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=mtahhan@redhat.com \
    --cc=thoiland@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox