From: Alexei Starovoitov <ast@fb.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>, Yonghong Song <yhs@fb.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Cong Wang <xiyou.wangcong@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <kernel-team@fb.com>,
Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCH bpf-next v4 05/12] bpf: add bpf_for_each_map_elem() helper
Date: Fri, 26 Feb 2021 11:27:49 -0800 [thread overview]
Message-ID: <964673c2-0bd4-02db-51a1-dc495a1b2d9b@fb.com> (raw)
In-Reply-To: <CAEf4Bza-EJ=AB0eMQLGomdmQNnN_PccaeoMk9HBmWaGfkh7enA@mail.gmail.com>
On 2/26/21 11:22 AM, Andrii Nakryiko wrote:
>> * long bpf_check_mtu(void *ctx, u32 ifindex, u32 *mtu_len, s32 len_diff, u64 flags)
>> * Description
>> -
> BTW, this was fixed in a7c9c25a99bb ("bpf: Remove blank line in bpf
> helper description comment") and applied to the bpf tree. Not sure if
> it will cause a merge conflict later. Maybe Alexei or Daniel can just
> add this line back while applying?
>
yeah. we'll cherry pick into bpf-next. It will get rebased anyway.
next prev parent reply other threads:[~2021-02-26 19:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 5:13 [PATCH bpf-next v4 00/12] bpf: add bpf_for_each_map_elem() helper Yonghong Song
2021-02-26 5:13 ` [PATCH bpf-next v4 01/12] bpf: factor out visit_func_call_insn() in check_cfg() Yonghong Song
2021-02-26 19:12 ` Andrii Nakryiko
2021-02-26 5:13 ` [PATCH bpf-next v4 02/12] bpf: factor out verbose_invalid_scalar() Yonghong Song
2021-02-26 5:13 ` [PATCH bpf-next v4 03/12] bpf: refactor check_func_call() to allow callback function Yonghong Song
2021-02-26 19:13 ` Andrii Nakryiko
2021-02-26 5:13 ` [PATCH bpf-next v4 04/12] bpf: change return value of verifier function add_subprog() Yonghong Song
2021-02-26 19:14 ` Andrii Nakryiko
2021-02-26 5:13 ` [PATCH bpf-next v4 05/12] bpf: add bpf_for_each_map_elem() helper Yonghong Song
2021-02-26 19:22 ` Andrii Nakryiko
2021-02-26 19:27 ` Alexei Starovoitov [this message]
2021-02-26 5:13 ` [PATCH bpf-next v4 06/12] bpf: add hashtab support for " Yonghong Song
2021-02-26 5:13 ` [PATCH bpf-next v4 07/12] bpf: add arraymap " Yonghong Song
2021-02-26 5:13 ` [PATCH bpf-next v4 08/12] libbpf: move function is_ldimm64() earlier in libbpf.c Yonghong Song
2021-02-26 5:13 ` [PATCH bpf-next v4 09/12] libbpf: support subprog address relocation Yonghong Song
2021-02-26 5:13 ` [PATCH bpf-next v4 10/12] bpftool: print subprog address properly Yonghong Song
2021-02-26 5:13 ` [PATCH bpf-next v4 11/12] selftests/bpf: add hashmap test for bpf_for_each_map_elem() helper Yonghong Song
2021-02-26 19:17 ` Andrii Nakryiko
2021-02-26 5:13 ` [PATCH bpf-next v4 12/12] selftests/bpf: add arraymap " Yonghong Song
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=964673c2-0bd4-02db-51a1-dc495a1b2d9b@fb.com \
--to=ast@fb.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yhs@fb.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