From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, amcohen@nvidia.com,
dsahern@gmail.com, ivecera@redhat.com, mlxsw@nvidia.com
Subject: Re: [PATCH net] selftests: forwarding: Fix failing tests with old libnet
Date: Thu, 11 Aug 2022 05:40:13 +0000 [thread overview]
Message-ID: <166019641371.21224.16931279962426380285.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220809113320.751413-1-idosch@nvidia.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 9 Aug 2022 14:33:20 +0300 you wrote:
> The custom multipath hash tests use mausezahn in order to test how
> changes in various packet fields affect the packet distribution across
> the available nexthops.
>
> The tool uses the libnet library for various low-level packet
> construction and injection. The library started using the
> "SO_BINDTODEVICE" socket option for IPv6 sockets in version 1.1.6 and
> for IPv4 sockets in version 1.2.
>
> [...]
Here is the summary with links:
- [net] selftests: forwarding: Fix failing tests with old libnet
https://git.kernel.org/netdev/net/c/8bcfb4ae4d97
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:[~2022-08-11 5:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 11:33 [PATCH net] selftests: forwarding: Fix failing tests with old libnet Ido Schimmel
2022-08-09 13:10 ` Jiri Pirko
2022-08-09 14:21 ` Petr Machata
2022-08-09 14:27 ` Ido Schimmel
2022-08-11 5:40 ` 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=166019641371.21224.16931279962426380285.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=ivecera@redhat.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).