From: patchwork-bot+netdevbpf@kernel.org
To: Justin Iurman <justin.iurman@uliege.be>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] selftests: net: ioam: add tunsrc support
Date: Fri, 04 Oct 2024 23:20:41 +0000 [thread overview]
Message-ID: <172808404149.2772330.14314026538003665489.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241002162731.19847-1-justin.iurman@uliege.be>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Oct 2024 18:27:29 +0200 you wrote:
> v2:
> - v1 missed the merge window, so while we're at it...
> - split changes into two patches instead of one for readability (#1
> removes the ioam selftests, #2 adds the updated ioam selftests)
>
> TL;DR This patch comes from a discussion we had with Jakub and Paolo on
> aligning the ioam selftests with its new "tunsrc" feature.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] selftests: net: remove ioam tests
https://git.kernel.org/netdev/net-next/c/897408d5e224
- [net-next,v2,2/2] selftests: net: add new ioam tests
https://git.kernel.org/netdev/net-next/c/2d2b5028b4ab
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-10-04 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 16:27 [PATCH net-next v2 0/2] selftests: net: ioam: add tunsrc support Justin Iurman
2024-10-02 16:27 ` [PATCH net-next v2 1/2] selftests: net: remove ioam tests Justin Iurman
2024-10-02 16:27 ` [PATCH net-next v2 2/2] selftests: net: add new " Justin Iurman
2024-10-04 23: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=172808404149.2772330.14314026538003665489.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=justin.iurman@uliege.be \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).