[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM0PR05MB4866F357E2116E1073E60BB2D1F10@AM0PR05MB4866.eurprd05.prod.outlook.com>
Date: Tue, 9 Jul 2019 19:21:47 +0000
From: Parav Pandit <parav@...lanox.com>
To: David Miller <davem@...emloft.net>,
"jakub.kicinski@...ronome.com" <jakub.kicinski@...ronome.com>
CC: "jiri@...nulli.us" <jiri@...nulli.us>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Jiri Pirko <jiri@...lanox.com>,
Saeed Mahameed <saeedm@...lanox.com>
Subject: RE: [PATCH net-next v6 0/5] devlink: Introduce PCI PF, VF ports and
attributes
Hi Dave,
> -----Original Message-----
> From: David Miller <davem@...emloft.net>
> Sent: Wednesday, July 10, 2019 12:34 AM
> To: jakub.kicinski@...ronome.com
> Cc: jiri@...nulli.us; Parav Pandit <parav@...lanox.com>;
> netdev@...r.kernel.org; Jiri Pirko <jiri@...lanox.com>; Saeed Mahameed
> <saeedm@...lanox.com>
> Subject: Re: [PATCH net-next v6 0/5] devlink: Introduce PCI PF, VF ports and
> attributes
>
> From: Jakub Kicinski <jakub.kicinski@...ronome.com>
> Date: Tue, 9 Jul 2019 11:20:58 -0700
>
> > On Tue, 9 Jul 2019 08:17:11 +0200, Jiri Pirko wrote:
> >> >But I'll leave it to Jiri and Dave to decide if its worth a respin
> >> >:) Functionally I think this is okay.
> >>
> >> I'm happy with the set as it is right now.
> >
> > To be clear, I am happy enough as well. Hence the review tag.
>
> Series applied, thanks everyone.
>
> >> Anyway, if you want your concerns to be addresses, you should write
> >> them to the appropriate code. This list is hard to follow.
> >
> > Sorry, I was trying to be concise.
>
> Jiri et al., if Jakub put forth the time and effort to make the list and give you
> feedback you can put forth the effort to go through the list and address his
> feedback with follow-up patches. You cannot dictate how people give
> feedback to your changes, thank you.
I will be happy to write follow up patches.
mostly in kernel 5.4, I will be adding mdev (mediated device) port flavour as discussed in past.
I will possibly write up follow up patch or two before posting them or have it in that series, as it will extend this devlink code further.
Powered by blists - more mailing lists