From: patchwork-bot+netdevbpf@kernel.org
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com,
alan.maguire@oracle.com, kpsingh@kernel.org, yatsenko@meta.com
Subject: Re: [PATCH bpf-next v3] selftests/bpf: Remove xxd util dependency
Date: Wed, 28 Jan 2026 21:30:04 +0000 [thread overview]
Message-ID: <176963580486.2238533.18301014240768634814.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260128190552.242335-1-mykyta.yatsenko5@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 28 Jan 2026 19:05:51 +0000 you wrote:
> From: Mykyta Yatsenko <yatsenko@meta.com>
>
> The verification signature header generation requires converting a
> binary certificate to a C array. Previously this only worked with
> xxd (part of vim-common package).
> As xxd may not be available on some systems building selftests, it makes
> sense to substitute it with more common utils: hexdump, wc, sed to
> generate equivalent C array output.
>
> [...]
Here is the summary with links:
- [bpf-next,v3] selftests/bpf: Remove xxd util dependency
https://git.kernel.org/bpf/bpf-next/c/b640d556a2b3
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:[~2026-01-28 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 19:05 [PATCH bpf-next v3] selftests/bpf: Remove xxd util dependency Mykyta Yatsenko
2026-01-28 21:30 ` 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=176963580486.2238533.18301014240768634814.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@meta.com \
--cc=kernel-team@meta.com \
--cc=kpsingh@kernel.org \
--cc=mykyta.yatsenko5@gmail.com \
--cc=yatsenko@meta.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