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
Subject: Re: [PATCH bpf-next v10 0/1] Document BPF_MAP_TYPE_ARRAY
Date: Fri, 11 Nov 2022 19:40:16 +0000 [thread overview]
Message-ID: <166819561626.2662.1576356651622652024.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221109174604.31673-1-donald.hunter@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 9 Nov 2022 17:46:03 +0000 you wrote:
> Add documentation for BPF_MAP_TYPE_ARRAY and BPF_MAP_TYPE_PERCPU_ARRAY
> variant, including kernel version introduced, usage and examples.
>
> v9->v10:
> - Add missing Reviewed-by tag
>
> v8->v9:
> - Add "Kernel BPF" heading suggested by Jesper Brouer
> - Tidy up wording to clarify BPF vs userspace APIs
>
> [...]
Here is the summary with links:
- [bpf-next,v10,1/1] bpf, docs: document BPF_MAP_TYPE_ARRAY
https://git.kernel.org/bpf/bpf-next/c/1cfa97b30c5a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-11 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 17:46 [PATCH bpf-next v10 0/1] Document BPF_MAP_TYPE_ARRAY Donald Hunter
2022-11-09 17:46 ` [PATCH bpf-next v10 1/1] bpf, docs: document BPF_MAP_TYPE_ARRAY Donald Hunter
2022-11-11 1:52 ` Bagas Sanjaya
2022-11-11 19:39 ` Andrii Nakryiko
2022-11-14 10:18 ` Donald Hunter
2022-11-14 19:44 ` Andrii Nakryiko
2022-11-11 19:40 ` patchwork-bot+netdevbpf [this message]
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=166819561626.2662.1576356651622652024.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 \
/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;
as well as URLs for NNTP newsgroup(s).