From: patchwork-bot+netdevbpf@kernel.org
To: Jakob Koschel <jakobkoschel@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, rppt@kernel.org,
bjohannesmeyer@gmail.com, c.giuffrida@vu.nl, h.j.bos@vu.nl
Subject: Re: [PATCH v2] bpf: replace usage of supported with dedicated list iterator variable
Date: Sun, 03 Apr 2022 23:40:10 +0000 [thread overview]
Message-ID: <164902921092.1167.516960967267677519.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220331091929.647057-1-jakobkoschel@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 31 Mar 2022 11:19:29 +0200 you wrote:
> To move the list iterator variable into the list_for_each_entry_*()
> macro in the future it should be avoided to use the list iterator
> variable after the loop body.
>
> To *never* use the list iterator variable after the loop it was
> concluded to use a separate iterator variable instead of a
> found boolean [1].
>
> [...]
Here is the summary with links:
- [v2] bpf: replace usage of supported with dedicated list iterator variable
https://git.kernel.org/bpf/bpf-next/c/185da3da9379
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-04-03 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 9:19 Jakob Koschel
2022-04-03 23: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=164902921092.1167.516960967267677519.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjohannesmeyer@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=c.giuffrida@vu.nl \
--cc=daniel@iogearbox.net \
--cc=h.j.bos@vu.nl \
--cc=jakobkoschel@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=songliubraving@fb.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
all inboxes | Powered by JetHome®