All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mohsin Bashir <mohsin.bashr@gmail.com>
To: netdev@vger.kernel.org
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
	ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
	john.fastabend@gmail.com, ap420073@gmail.com,
	linux-kselftest@vger.kernel.org
Subject: [PATCH net 0/3 v4] selftests: drv: net: fix `ping.py` test failure
Date: Fri,  2 May 2025 18:35:15 -0700	[thread overview]
Message-ID: <20250503013518.1722913-1-mohsin.bashr@gmail.com> (raw)

Fix `ping.py` test failure on an ipv6 system, and appropriately handle the
cases where either one of the two address families (ipv4, ipv6) is not
present.

Mohsin Bashir (3):
  selftests: drv: net: fix test failure on ipv6 sys
  selftests: drv: net: avoid skipping tests
  selftests: drv: net: add version indicator

 tools/testing/selftests/drivers/net/ping.py | 45 ++++++++++++---------
 1 file changed, 27 insertions(+), 18 deletions(-)

-- 
2.47.1


             reply	other threads:[~2025-05-03  1:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-03  1:35 Mohsin Bashir [this message]
2025-05-03  1:35 ` [PATCH net 1/3] selftests: drv: net: fix test failure on ipv6 sys Mohsin Bashir
2025-05-03  4:49   ` David Wei
2025-05-05 17:44     ` Jakub Kicinski
2025-05-03  1:35 ` [PATCH net 2/3] selftests: drv: net: avoid skipping tests Mohsin Bashir
2025-05-03  4:54   ` David Wei
2025-05-05 17:47     ` Jakub Kicinski
2025-05-05 18:12       ` David Wei
2025-05-05 18:19         ` David Wei
2025-05-03  1:35 ` [PATCH net 3/3] selftests: drv: net: add version indicator Mohsin Bashir
2025-05-03  5:02   ` David Wei
2025-05-05 17:49     ` Jakub Kicinski
2025-05-05 18:25       ` David Wei
2025-05-06  1:20 ` [PATCH net 0/3 v4] selftests: drv: net: fix `ping.py` test failure 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=20250503013518.1722913-1-mohsin.bashr@gmail.com \
    --to=mohsin.bashr@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=ap420073@gmail.com \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@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 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.