From: Mohsin Bashir <mohsin.bashr@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
shuah@kernel.org, horms@kernel.org, cratiu@nvidia.com,
noren@nvidia.com, cjubran@nvidia.com, mbloch@nvidia.com,
jdamato@fastly.com, gal@nvidia.com, sdf@fomichev.me,
ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
john.fastabend@gmail.com, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next V3 0/4] selftests: drv-net: Test XDP native support
Date: Sun, 13 Jul 2025 12:11:28 -0700 [thread overview]
Message-ID: <2311adfb-e3be-44dc-b724-1af18c3e50a1@gmail.com> (raw)
In-Reply-To: <20250712080254.4ed08842@kernel.org>
> Hm, but we need a netdevsim patch to support XDP to be part of this
> series. Right now our CI tries to run it against netdevsim and all
> the tests fail.
Yes, we do need that for netdevsim. Should we make part of this series,
or hold this one until it lands?
prev parent reply other threads:[~2025-07-13 19:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-12 0:26 [PATCH net-next V3 0/4] selftests: drv-net: Test XDP native support Mohsin Bashir
2025-07-12 0:26 ` [PATCH net-next V3 1/4] selftests: drv-net: Test XDP_PASS/DROP support Mohsin Bashir
2025-07-12 9:25 ` Muhammad Usama Anjum
2025-07-12 14:58 ` Jakub Kicinski
2025-07-13 19:09 ` Mohsin Bashir
2025-07-12 0:26 ` [PATCH net-next V3 2/4] selftests: drv-net: Test XDP_TX support Mohsin Bashir
2025-07-12 0:26 ` [PATCH net-next V3 3/4] selftests: drv-net: Test tail-adjustment support Mohsin Bashir
2025-07-12 0:26 ` [PATCH net-next V3 4/4] selftests: drv-net: Test head-adjustment support Mohsin Bashir
2025-07-12 15:00 ` Jakub Kicinski
2025-07-12 15:02 ` [PATCH net-next V3 0/4] selftests: drv-net: Test XDP native support Jakub Kicinski
2025-07-13 19:11 ` Mohsin Bashir [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=2311adfb-e3be-44dc-b724-1af18c3e50a1@gmail.com \
--to=mohsin.bashr@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cjubran@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=jdamato@fastly.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--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).