From: Petr Machata <petrm@nvidia.com>
To: Petr Machata <petrm@nvidia.com>
Cc: Jiri Pirko <jiri@resnulli.us>, <netdev@vger.kernel.org>,
<kuba@kernel.org>, <pabeni@redhat.com>, <davem@davemloft.net>,
<edumazet@google.com>, <parav@nvidia.com>, <mst@redhat.com>,
<jasowang@redhat.com>, <xuanzhuo@linux.alibaba.com>,
<shuah@kernel.org>, <liuhangbin@gmail.com>,
<vladimir.oltean@nxp.com>, <bpoirier@nvidia.com>,
<idosch@nvidia.com>, <virtualization@lists.linux.dev>
Subject: Re: [patch net-next v3 3/6] selftests: forwarding: add ability to assemble NETIFS array by driver name
Date: Thu, 18 Apr 2024 10:43:44 +0200 [thread overview]
Message-ID: <87y19bawl2.fsf@nvidia.com> (raw)
In-Reply-To: <87bk67cbuc.fsf@nvidia.com>
Petr Machata <petrm@nvidia.com> writes:
> Jiri Pirko <jiri@resnulli.us> writes:
>
>> +# Whether to find netdevice according to the specified driver.
>> +: "${NETIF_FIND_DRIVER:=}"
>
> This would be better placed up there in the Topology description
> section. Together with NETIFS and NETIF_NO_CABLE, as it concerns
> specification of which interfaces to use.
Oh never mind, it's not something a user should configure, but rather a
test API.
next prev parent reply other threads:[~2024-04-18 8:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 16:45 [patch net-next v3 0/6] selftests: virtio_net: introduce initial testing infrastructure Jiri Pirko
2024-04-17 16:45 ` [patch net-next v3 1/6] virtio: add debugfs infrastructure to allow to debug virtio features Jiri Pirko
2024-04-17 16:45 ` [patch net-next v3 2/6] selftests: forwarding: move couple of initial check to the beginning Jiri Pirko
2024-04-17 18:58 ` Benjamin Poirier
2024-04-18 6:16 ` Jiri Pirko
2024-04-17 16:45 ` [patch net-next v3 3/6] selftests: forwarding: add ability to assemble NETIFS array by driver name Jiri Pirko
2024-04-18 8:11 ` Petr Machata
2024-04-18 8:43 ` Petr Machata [this message]
2024-04-18 12:01 ` Jiri Pirko
2024-04-18 12:14 ` Jiri Pirko
2024-04-17 16:45 ` [patch net-next v3 4/6] selftests: forwarding: add check_driver() helper Jiri Pirko
2024-04-18 8:31 ` Petr Machata
2024-04-17 16:45 ` [patch net-next v3 5/6] selftests: forwarding: add wait_for_dev() helper Jiri Pirko
2024-04-18 8:33 ` Petr Machata
2024-04-18 12:01 ` Jiri Pirko
2024-04-17 16:45 ` [patch net-next v3 6/6] selftests: virtio_net: add initial tests Jiri Pirko
2024-04-18 8:39 ` Petr Machata
2024-04-18 12:00 ` Jiri Pirko
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=87y19bawl2.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=bpoirier@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=jasowang@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=shuah@kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=vladimir.oltean@nxp.com \
--cc=xuanzhuo@linux.alibaba.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).