[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM0PR05MB4866CBFB93C42453068376DED1F80@AM0PR05MB4866.eurprd05.prod.outlook.com>
Date: Tue, 2 Jul 2019 17:18:52 +0000
From: Parav Pandit <parav@...lanox.com>
To: Andrew Lunn <andrew@...n.ch>
CC: Sudarsana Reddy Kalluru <skalluru@...vell.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"mkalderon@...vell.com" <mkalderon@...vell.com>,
"aelior@...vell.com" <aelior@...vell.com>,
"jiri@...nulli.us" <jiri@...nulli.us>
Subject: RE: [PATCH net-next 1/1] devlink: Add APIs to publish/unpublish the
port parameters.
> -----Original Message-----
> From: Andrew Lunn <andrew@...n.ch>
> Sent: Tuesday, July 2, 2019 10:19 PM
> To: Parav Pandit <parav@...lanox.com>
> Cc: Sudarsana Reddy Kalluru <skalluru@...vell.com>; davem@...emloft.net;
> netdev@...r.kernel.org; mkalderon@...vell.com; aelior@...vell.com;
> jiri@...nulli.us
> Subject: Re: [PATCH net-next 1/1] devlink: Add APIs to publish/unpublish the
> port parameters.
>
> > A vendor driver calling these APIs is needed at minimum.
>
> Not a vendor driver, but a mainline driver.
>
My apologies for terminology.
I meant to say that a NIC/hw driver from the kernel tree that created the devlink port should call this API (as user) in the patch.
You said it rightly below. Thanks.
> But yes, a new API should not be added without at least one user.
>
> Andrew
Powered by blists - more mailing lists