[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY5PR12MB43224CC697D1C9BE23CC8D6ADCE00@BY5PR12MB4322.namprd12.prod.outlook.com>
Date: Thu, 19 Nov 2020 08:25:24 +0000
From: Parav Pandit <parav@...dia.com>
To: Saeed Mahameed <saeed@...nel.org>,
Jakub Kicinski <kuba@...nel.org>,
"Jason Gunthorpe" <jgg@...dia.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
Jiri Pirko <jiri@...dia.com>,
"dledford@...hat.com" <dledford@...hat.com>,
"Leon Romanovsky" <leonro@...dia.com>,
"davem@...emloft.net" <davem@...emloft.net>
Subject: RE: [PATCH net-next 00/13] Add mlx5 subfunction support
> From: Saeed Mahameed <saeed@...nel.org>
> Sent: Thursday, November 19, 2020 11:42 AM
>
> From how this discussion is going, i think you are right, we need to clarify
> what we are doing in a more high level simplified and generic documentation
> to give some initial context, Parav, let's add the missing documentation, we
> can also add some comments regarding how this is very different from
> VMDq, but i would like to avoid that, since it is different in almost every way:)
Sure I will add Documentation/networking/subfunction.rst in v2 describing subfunction details.
Powered by blists - more mailing lists