From: Yonghong Song <yhs@meta.com>
To: Donald Hunter <donald.hunter@gmail.com>,
bpf@vger.kernel.org, linux-doc@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH bpf-next v3] docs/bpf: Document BPF map types QUEUE and STACK
Date: Tue, 8 Nov 2022 06:39:49 -0800 [thread overview]
Message-ID: <afef6c5a-1ec4-9a9b-adec-aaed31f11d14@meta.com> (raw)
In-Reply-To: <20221108093314.44851-1-donald.hunter@gmail.com>
On 11/8/22 1:33 AM, Donald Hunter wrote:
> Add documentation for BPF_MAP_TYPE_QUEUE and BPF_MAP_TYPE_STACK,
> including usage and examples.
>
> Signed-off-by: Donald Hunter <donald.hunter@gmail.com>
Acked-by: Yonghong Song <yhs@fb.com>
next prev parent reply other threads:[~2022-11-08 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 9:33 [PATCH bpf-next v3] docs/bpf: Document BPF map types QUEUE and STACK Donald Hunter
2022-11-08 12:57 ` [PATCH " Bagas Sanjaya
2022-11-08 14:50 ` Yonghong Song
2022-11-08 14:39 ` Yonghong Song [this message]
2022-11-11 19:40 ` [PATCH bpf-next " 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=afef6c5a-1ec4-9a9b-adec-aaed31f11d14@meta.com \
--to=yhs@meta.com \
--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