From: patchwork-bot+netdevbpf@kernel.org
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: john.fastabend@gmail.com, kpsingh@kernel.org, jolsa@kernel.org,
martin.lau@linux.dev, daniel@iogearbox.net, haoluo@google.com,
yhs@fb.com, andrii@kernel.org, ast@kernel.org, song@kernel.org,
sdf@google.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bpf: Remove unused field initialization
Date: Thu, 22 Dec 2022 15:00:16 +0000 [thread overview]
Message-ID: <167172121630.11988.10950237578875871796.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221221-bpf-syscall-v1-0-9550f5f2c3fc@chromium.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 21 Dec 2022 20:55:29 +0100 you wrote:
> Maxlen is used by standard proc_handlers such as proc_dointvec(), but in this
> case we have our own proc_handler. Remove the initialization.
>
> Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
> ---
> bpf: Trivial remove of unitialised field.
>
> [...]
Here is the summary with links:
- bpf: Remove unused field initialization
https://git.kernel.org/bpf/bpf-next/c/cfca00767feb
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-12-22 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 19:55 [PATCH] bpf: Remove unused field initialization Ricardo Ribalda
2022-12-21 20:10 ` Stanislav Fomichev
2022-12-21 20:13 ` Ricardo Ribalda
2022-12-21 20:18 ` Stanislav Fomichev
2022-12-22 15: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=167172121630.11988.10950237578875871796.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=ribalda@chromium.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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