[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <PH0PR12MB5481F93DA9B6AA3C573E64C1DC609@PH0PR12MB5481.namprd12.prod.outlook.com>
Date: Tue, 23 Nov 2021 05:19:28 +0000
From: Parav Pandit <parav@...dia.com>
To: Tony Nguyen <anthony.l.nguyen@...el.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>
CC: Shiraz Saleem <shiraz.saleem@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"mustafa.ismail@...el.com" <mustafa.ismail@...el.com>,
"jacob.e.keller@...el.com" <jacob.e.keller@...el.com>,
Jiri Pirko <jiri@...dia.com>,
Leszek Kaliszczuk <leszek.kaliszczuk@...el.com>
Subject: RE: [PATCH net-next 2/3] net/ice: Add support for enable_iwarp and
enable_roce devlink param
> From: Tony Nguyen <anthony.l.nguyen@...el.com>
> Sent: Tuesday, November 23, 2021 2:41 AM
>
> From: Shiraz Saleem <shiraz.saleem@...el.com>
>
> Allow support for 'enable_iwarp' and 'enable_roce' devlink params to turn
> on/off iWARP or RoCE protocol support for E800 devices.
It is better to split this patch to two as there are two functionalities done here.
1. enable/disable roce as first patch
2. enable/disable iwarp as 2nd patch
But I don't feel strong about it, as both has some inter dependency on checking other capabilities, so either way is fine.
If you can split, it will be good.
Powered by blists - more mailing lists