From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
petrm@nvidia.com, bpoirier@nvidia.com, liuhangbin@gmail.com,
idosch@nvidia.com, jiri@resnulli.us,
linux-kselftest@vger.kernel.org, troglobit@gmail.com
Subject: Re: [PATCH net-next] selftests: net: use upstream mtools
Date: Mon, 13 May 2024 21:00:30 +0000 [thread overview]
Message-ID: <171563403068.25832.3366829095151395846.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240510112856.1262901-1-vladimir.oltean@nxp.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 10 May 2024 14:28:56 +0300 you wrote:
> Joachim kindly merged the IPv6 support in
> https://github.com/troglobit/mtools/pull/2, so we can just use his
> version now. A few more fixes subsequently came in for IPv6, so even
> better.
>
> Check that the deployed mtools version is 3.0 or above. Note that the
> version check breaks compatibility with my fork where I didn't bump the
> version, but I assume that won't be a problem.
>
> [...]
Here is the summary with links:
- [net-next] selftests: net: use upstream mtools
https://git.kernel.org/netdev/net-next/c/cfc2eefd40f1
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-05-13 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 11:28 [PATCH net-next] selftests: net: use upstream mtools Vladimir Oltean
2024-05-10 14:24 ` Jakub Kicinski
2024-05-10 15:34 ` Vladimir Oltean
2024-05-13 21: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=171563403068.25832.3366829095151395846.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpoirier@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=shuah@kernel.org \
--cc=troglobit@gmail.com \
--cc=vladimir.oltean@nxp.com \
/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).