From: patchwork-bot+netdevbpf@kernel.org
To: Marcos Paulo de Souza <mpdesouza@suse.com>
Cc: andrii@kernel.org, eddyz87@gmail.com, mykolal@fb.com,
ast@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests: bpf: Remove empty TEST_CUSTOM_PROGS
Date: Fri, 16 Feb 2024 17:20:25 +0000 [thread overview]
Message-ID: <170810402550.3129.12516651246134620322.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240216-bpf-selftests-custom-progs-v1-1-f7cf281a1fda@suse.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 16 Feb 2024 09:42:45 -0300 you wrote:
> Commit f04a32b2c5b5 ("selftests/bpf: Do not use sign-file as testcase")
> removed the TEST_CUSTOM_PROGS assignment, and removed it from being used
> on TEST_GEN_FILES. Remove two leftovers from that cleanup.
>
> Found by inspection.
>
> Signed-off-by: Marcos Paulo de Souza <mpdesouza@suse.com>
>
> [...]
Here is the summary with links:
- [bpf-next] selftests: bpf: Remove empty TEST_CUSTOM_PROGS
https://git.kernel.org/bpf/bpf-next/c/7648f0c91eaa
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-02-16 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 12:42 [PATCH bpf-next] selftests: bpf: Remove empty TEST_CUSTOM_PROGS Marcos Paulo de Souza
2024-02-16 17:20 ` 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=170810402550.3129.12516651246134620322.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=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mpdesouza@suse.com \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--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