From: patchwork-bot+netdevbpf@kernel.org
To: Dr. David Alan Gilbert <linux@treblig.org>
Cc: andrii@kernel.org, eddyz87@gmail.com, mykolal@fb.com,
kpsingh@kernel.org, shuah@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Dead structs in tools/testing/selftests/bpf
Date: Mon, 03 Jun 2024 15:00:31 +0000 [thread overview]
Message-ID: <171742683133.27164.9364551031995074993.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240602234112.225107-1-linux@treblig.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 3 Jun 2024 00:41:09 +0100 you wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
> Hi,
> Clean out a bunch of old structs in selftests/bpf.
> I've been using a 'make test_progs' as a build test.
>
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
>
> [...]
Here is the summary with links:
- [1/3] selftests/bpf: remove unused struct 'scale_test_def'
https://git.kernel.org/bpf/bpf-next/c/dfa7c9ffa607
- [2/3] selftests/bpf: remove unused 'key_t' structs
https://git.kernel.org/bpf/bpf-next/c/3f67639d8e58
- [3/3] selftests/bpf: remove unused struct 'libcap'
https://git.kernel.org/bpf/bpf-next/c/a450d36b05fa
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-06-03 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 23:41 [PATCH 0/3] Dead structs in tools/testing/selftests/bpf linux
2024-06-02 23:41 ` [PATCH 1/3] selftests/bpf: remove unused struct 'scale_test_def' linux
2024-06-02 23:41 ` [PATCH 2/3] selftests/bpf: remove unused 'key_t' structs linux
2024-06-02 23:41 ` [PATCH 3/3] selftests/bpf: remove unused struct 'libcap' linux
2024-06-03 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=171742683133.27164.9364551031995074993.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mykolal@fb.com \
--cc=shuah@kernel.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