From: patchwork-bot+netdevbpf@kernel.org
To: Markus Elfring <Markus.Elfring@web.de>
Cc: bpf@vger.kernel.org, kernel-janitors@vger.kernel.org,
ast@kernel.org, andrii@kernel.org, christophe.jaillet@wanadoo.fr,
daniel@iogearbox.net, eddyz87@gmail.com, haoluo@google.com,
jolsa@kernel.org, john.fastabend@gmail.com, kpsingh@kernel.org,
martin.lau@linux.dev, song@kernel.org, sdf@fomichev.me,
yonghong.song@linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bpf: Simplify character output in seq_print_delegate_opts()
Date: Fri, 19 Jul 2024 17:40:32 +0000 [thread overview]
Message-ID: <172141083222.15079.8073585538848691989.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <abde0992-3d71-44d2-ab27-75b382933a22@web.de>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 15 Jul 2024 11:20:27 +0200 you wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Mon, 15 Jul 2024 11:12:30 +0200
>
> Single characters should be put into a sequence.
> Thus use the corresponding function “seq_putc” for two selected calls.
>
> This issue was transformed by using the Coccinelle software.
>
> [...]
Here is the summary with links:
- bpf: Simplify character output in seq_print_delegate_opts()
https://git.kernel.org/bpf/bpf-next/c/51f1bb929647
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:[~2024-07-19 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 9:20 [PATCH] bpf: Simplify character output in seq_print_delegate_opts() Markus Elfring
2024-07-19 17: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=172141083222.15079.8073585538848691989.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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.