From: Paolo Abeni <pabeni@redhat.com>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>,
mptcp@lists.linux.dev, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Shuah Khan <shuah@kernel.org>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH net-next] selftests: drv-net: fix merge conflicts resolution
Date: Fri, 14 Mar 2025 10:27:56 +0100 [thread overview]
Message-ID: <0a205f79-b0b5-4cd6-b237-3c61b61bc806@redhat.com> (raw)
In-Reply-To: <20250314-net-next-drv-net-ping-fix-merge-v1-1-0d5c19daf707@kernel.org>
On 3/14/25 9:35 AM, Matthieu Baerts (NGI0) wrote:
> After the recent merge between net-next and net, I got some conflicts on
> my side because the merge resolution was different from Stephen's one
> [1] I applied on my side in the MPTCP tree.
>
> It looks like the code that is now in net-next is using the old way to
> retrieve the local and remote addresses. This patch is now using the new
> way, like what was in Stephen's email [1].
>
> Also, in get_interface_info(), there were no conflicts in this area,
> because that was new code from 'net', but a small adaptation was needed
> there as well to get the remote address.
>
> Fixes: 941defcea7e1 ("Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net")
> Link: https://lore.kernel.org/20250311115758.17a1d414@canb.auug.org.au [1]
> Suggested-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> ---
> tools/testing/selftests/drivers/net/ping.py | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/tools/testing/selftests/drivers/net/ping.py b/tools/testing/selftests/drivers/net/ping.py
> index 7a1026a073681d159202015fc6945e91368863fe..79f07e0510ecc14d3bc2716e14f49f9381bb919f 100755
> --- a/tools/testing/selftests/drivers/net/ping.py
> +++ b/tools/testing/selftests/drivers/net/ping.py
> @@ -15,18 +15,18 @@ no_sleep=False
> def _test_v4(cfg) -> None:
> cfg.require_ipver("4")
>
> - cmd(f"ping -c 1 -W0.5 {cfg.remote_v4}")
> - cmd(f"ping -c 1 -W0.5 {cfg.v4}", host=cfg.remote)
> - cmd(f"ping -s 65000 -c 1 -W0.5 {cfg.remote_v4}")
> - cmd(f"ping -s 65000 -c 1 -W0.5 {cfg.v4}", host=cfg.remote)
> + cmd("ping -c 1 -W0.5 " + cfg.remote_addr_v["4"])
> + cmd("ping -c 1 -W0.5 " + cfg.addr_v["4"], host=cfg.remote)
> + cmd("ping -s 65000 -c 1 -W0.5 " + cfg.remote_addr_v["4"])
> + cmd("ping -s 65000 -c 1 -W0.5 " + cfg.addr_v["4"], host=cfg.remote)
>
> def _test_v6(cfg) -> None:
> cfg.require_ipver("6")
>
> - cmd(f"ping -c 1 -W5 {cfg.remote_v6}")
> - cmd(f"ping -c 1 -W5 {cfg.v6}", host=cfg.remote)
> - cmd(f"ping -s 65000 -c 1 -W0.5 {cfg.remote_v6}")
> - cmd(f"ping -s 65000 -c 1 -W0.5 {cfg.v6}", host=cfg.remote)
> + cmd("ping -c 1 -W5 " + cfg.remote_addr_v["6"])
> + cmd("ping -c 1 -W5 " + cfg.addr_v["6"], host=cfg.remote)
> + cmd("ping -s 65000 -c 1 -W0.5 " + cfg.remote_addr_v["6"])
> + cmd("ping -s 65000 -c 1 -W0.5 " + cfg.addr_v["6"], host=cfg.remote)
>
> def _test_tcp(cfg) -> None:
> cfg.require_cmd("socat", remote=True)
> @@ -120,7 +120,7 @@ def get_interface_info(cfg) -> None:
> global remote_ifname
> global no_sleep
>
> - remote_info = cmd(f"ip -4 -o addr show to {cfg.remote_v4} | awk '{{print $2}}'", shell=True, host=cfg.remote).stdout
> + remote_info = cmd(f"ip -4 -o addr show to {cfg.remote_addr_v['4']} | awk '{{print $2}}'", shell=True, host=cfg.remote).stdout
> remote_ifname = remote_info.rstrip('\n')
> if remote_ifname == "":
> raise KsftFailEx('Can not get remote interface')
Thanks for the very quick turnaround!
It really solves the mess I did.
Exceptionally applying (well) before the 24h grace period to keep the
tree sane.
Thanks!
Paolo
next prev parent reply other threads:[~2025-03-14 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 8:35 [PATCH net-next] selftests: drv-net: fix merge conflicts resolution Matthieu Baerts (NGI0)
2025-03-14 9:27 ` Paolo Abeni [this message]
2025-03-14 9:30 ` patchwork-bot+netdevbpf
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=0a205f79-b0b5-4cd6-b237-3c61b61bc806@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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