From: patchwork-bot+netdevbpf@kernel.org
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org,
andrii@kernel.org, lorenzo.bianconi@redhat.com,
daniel@iogearbox.net
Subject: Re: [PATCH bpf-next v2 0/2] selftests/bpf: use ifname instead of ifindex in XDP
Date: Thu, 09 Mar 2023 20:00:17 +0000 [thread overview]
Message-ID: <167839201795.28882.17670469043875720414.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1678382940.git.lorenzo@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 9 Mar 2023 18:32:39 +0100 you wrote:
> Use interface name instead of interface index in XDP compliance test tool logs.
> Improve XDP compliance test tool error messages.
>
> Changes since v1:
> - split previous patch in two logically separated patches
>
> Lorenzo Bianconi (2):
> selftests/bpf: use ifname instead of ifindex in XDP compliance test
> tool
> selftests/bpf: improve error logs in XDP compliance test tool
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] selftests/bpf: use ifname instead of ifindex in XDP compliance test tool
https://git.kernel.org/bpf/bpf-next/c/27a36bc3cdd5
- [bpf-next,v2,2/2] selftests/bpf: improve error logs in XDP compliance test tool
https://git.kernel.org/bpf/bpf-next/c/c1cd734c1bb3
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:[~2023-03-09 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 17:32 [PATCH bpf-next v2 0/2] selftests/bpf: use ifname instead of ifindex in XDP Lorenzo Bianconi
2023-03-09 17:32 ` [PATCH bpf-next v2 1/2] selftests/bpf: use ifname instead of ifindex in XDP compliance test tool Lorenzo Bianconi
2023-03-09 17:32 ` [PATCH bpf-next v2 2/2] selftests/bpf: improve error logs " Lorenzo Bianconi
2023-03-09 20: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=167839201795.28882.17670469043875720414.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=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.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 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.