From: patchwork-bot+netdevbpf@kernel.org
To: Florent Revest <revest@chromium.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kpsingh@kernel.org, jackmanb@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf 1/2] bpf: Clarify a bpf_bprintf_prepare macro
Date: Mon, 17 May 2021 18:10:09 +0000 [thread overview]
Message-ID: <162127500989.31294.344588997595875629.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210517092830.1026418-1-revest@chromium.org>
Hello:
This series was applied to bpf/bpf.git (refs/heads/master):
On Mon, 17 May 2021 11:28:29 +0200 you wrote:
> The per-cpu buffers contain bprintf data rather than printf arguments.
> The macro name and comment were a bit confusing, this rewords them in a
> clearer way.
>
> Signed-off-by: Florent Revest <revest@chromium.org>
> ---
> kernel/bpf/helpers.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
Here is the summary with links:
- [bpf,1/2] bpf: Clarify a bpf_bprintf_prepare macro
https://git.kernel.org/bpf/bpf/c/8ba1030385e3
- [bpf,2/2] bpf: Avoid using ARRAY_SIZE on an uninitialized pointer
https://git.kernel.org/bpf/bpf/c/d0c0fe10ce6d
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:[~2021-05-17 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 9:28 Florent Revest
2021-05-17 9:28 ` [PATCH bpf 2/2] bpf: Avoid using ARRAY_SIZE on an uninitialized pointer Florent Revest
2021-05-17 17:54 ` Song Liu
2021-05-17 17:54 ` [PATCH bpf 1/2] bpf: Clarify a bpf_bprintf_prepare macro Song Liu
2021-05-17 18:10 ` 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=162127500989.31294.344588997595875629.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=jackmanb@google.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=revest@chromium.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
all inboxes | Powered by JetHome®