BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alan Maguire <alan.maguire@oracle.com>
Cc: qmo@kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, kpsingh@kernel.org, sdf@fomichev.me,
	yonghong.song@linux.dev, song@kernel.org, haoluo@google.com,
	jolsa@kernel.org, ihor.solodrai@linux.dev,
	john.fastabend@gmail.com, eddyz87@gmail.com, bpf@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Ease BPF signing build requirements
Date: Mon, 24 Nov 2025 18:30:09 +0000	[thread overview]
Message-ID: <176400900979.36456.12257313690030895068.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251120084754.640405-1-alan.maguire@oracle.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu, 20 Nov 2025 08:47:52 +0000 you wrote:
> This series makes it easier to build bpftool and selftests with
> signing support, removing reliance on >= openssl v3 (supporting
> openssl v1) to build bpftool and not requiring latest xxd to
> build verification cert header in selftests.
> 
> Changes since v1 [1]:
> 
> [...]

Here is the summary with links:
  - [v2,1/2] bpftool: Allow bpftool to build with openssl < 3
    https://git.kernel.org/bpf/bpf-next/c/90ae54b4c7ec
  - [v2,2/2] selftests/bpf: Allow selftests to build with older xxd
    https://git.kernel.org/bpf/bpf-next/c/ad93ba02678e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-11-24 18:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20  8:47 [PATCH v2 0/2] Ease BPF signing build requirements Alan Maguire
2025-11-20  8:47 ` [PATCH v2 1/2] bpftool: Allow bpftool to build with openssl < 3 Alan Maguire
2025-11-20  8:47 ` [PATCH v2 2/2] selftests/bpf: Allow selftests to build with older xxd Alan Maguire
2025-11-24 18: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=176400900979.36456.12257313690030895068.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=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=qmo@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox