From: patchwork-bot+netdevbpf@kernel.org
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
johan.almbladh@anyfinetworks.com, paulburton@kernel.org,
tsbogend@alpha.franken.de, bpf@vger.kernel.org,
linux-mips@vger.kernel.org
Subject: Re: [PATCH bpf-next v2] bpf, mips: No need to use min() to get MAX_TAIL_CALL_CNT
Date: Mon, 29 Aug 2022 14:00:16 +0000 [thread overview]
Message-ID: <166178161672.22044.323887276798287961.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1661742309-2320-1-git-send-email-yangtiezhu@loongson.cn>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 29 Aug 2022 11:05:09 +0800 you wrote:
> MAX_TAIL_CALL_CNT is 33, so min(MAX_TAIL_CALL_CNT, 0xffff) is always
> MAX_TAIL_CALL_CNT, it is better to use MAX_TAIL_CALL_CNT directly.
>
> At the same time, add BUILD_BUG_ON(MAX_TAIL_CALL_CNT > 0xffff) with a
> comment on why the assertion is there.
>
> Suggested-by: Daniel Borkmann <daniel@iogearbox.net>
> Suggested-by: Johan Almbladh <johan.almbladh@anyfinetworks.com>
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf, mips: No need to use min() to get MAX_TAIL_CALL_CNT
https://git.kernel.org/bpf/bpf-next/c/bbcf0f55e578
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-08-29 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 3:05 [PATCH bpf-next v2] bpf, mips: No need to use min() to get MAX_TAIL_CALL_CNT Tiezhu Yang
2022-08-29 14:00 ` 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=166178161672.22044.323887276798287961.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=daniel@iogearbox.net \
--cc=johan.almbladh@anyfinetworks.com \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=yangtiezhu@loongson.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.