[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y19bawl2.fsf@nvidia.com>
Date: Thu, 18 Apr 2024 10:43:44 +0200
From: Petr Machata <petrm@...dia.com>
To: Petr Machata <petrm@...dia.com>
CC: Jiri Pirko <jiri@...nulli.us>, <netdev@...r.kernel.org>,
<kuba@...nel.org>, <pabeni@...hat.com>, <davem@...emloft.net>,
<edumazet@...gle.com>, <parav@...dia.com>, <mst@...hat.com>,
<jasowang@...hat.com>, <xuanzhuo@...ux.alibaba.com>, <shuah@...nel.org>,
<liuhangbin@...il.com>, <vladimir.oltean@....com>, <bpoirier@...dia.com>,
<idosch@...dia.com>, <virtualization@...ts.linux.dev>
Subject: Re: [patch net-next v3 3/6] selftests: forwarding: add ability to
assemble NETIFS array by driver name
Petr Machata <petrm@...dia.com> writes:
> Jiri Pirko <jiri@...nulli.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.
Powered by blists - more mailing lists