[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZiELtgonxSFIfX5H@nanopsycho>
Date: Thu, 18 Apr 2024 14:01:58 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Petr Machata <petrm@...dia.com>
Cc: 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
Thu, Apr 18, 2024 at 10:43:44AM CEST, petrm@...dia.com wrote:
>
>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.
Yep.
Powered by blists - more mailing lists