From: patchwork-bot+netdevbpf@kernel.org
To: Donald Hunter <donald.hunter@gmail.com>
Cc: bpf@vger.kernel.org, linux-doc@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, corbet@lwn.net,
yhs@meta.com, void@manifault.com
Subject: Re: [PATCH bpf-next v4] docs/bpf: Add documentation for BPF_MAP_TYPE_SK_STORAGE
Date: Fri, 09 Dec 2022 17:50:15 +0000 [thread overview]
Message-ID: <167060821547.31126.2706063406083427383.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221209112401.69319-1-donald.hunter@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 9 Dec 2022 11:24:01 +0000 you wrote:
> Add documentation for the BPF_MAP_TYPE_SK_STORAGE including
> kernel version introduced, usage and examples.
>
> Signed-off-by: Donald Hunter <donald.hunter@gmail.com>
> ---
> v3 -> v4:
> - Update intro paragraph with detail about storage locality.
> - Remove confusing text from bpf_map_update_elem()
> as reported by David Vernet
> - Updated BPF_EXIST and BPF_NOEXIST behaviour as suggested
> by David Vernet
> - Fixed extra space in function signature as reported by
> David Vernet
> - Added reference to selftests for complete examples as
> suggested by Yonghong Song
> v2 -> v3:
> - Fix void * return, reported by Yonghong Song
> - Add tracing programs to API note, reported by Yonghong Song
> v1 -> v2:
> - Fix bpf_sk_storage_* function signatures, reported by Yonghong Song
> - Fix NULL return on failure, reported by Yonghong Song
>
> [...]
Here is the summary with links:
- [bpf-next,v4] docs/bpf: Add documentation for BPF_MAP_TYPE_SK_STORAGE
https://git.kernel.org/bpf/bpf-next/c/f3212ad5b7e9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-12-09 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 11:24 [PATCH bpf-next v4] docs/bpf: Add documentation for BPF_MAP_TYPE_SK_STORAGE Donald Hunter
2022-12-09 16:14 ` David Vernet
2022-12-09 17:50 ` patchwork-bot+netdevbpf [this message]
2022-12-09 17:52 ` Martin KaFai Lau
2022-12-09 17:54 ` Alexei Starovoitov
2022-12-09 17:58 ` Martin KaFai Lau
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=167060821547.31126.2706063406083427383.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=donald.hunter@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=void@manifault.com \
--cc=yhs@meta.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