[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190710064143.GB2282@nanopsycho>
Date: Wed, 10 Jul 2019 08:41:43 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: David Miller <davem@...emloft.net>
Cc: jakub.kicinski@...ronome.com, parav@...lanox.com,
netdev@...r.kernel.org, jiri@...lanox.com, saeedm@...lanox.com
Subject: Re: [PATCH net-next v6 0/5] devlink: Introduce PCI PF, VF ports and
attributes
Tue, Jul 09, 2019 at 09:03:36PM CEST, davem@...emloft.net wrote:
>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 don't want to do such thing. I'm just saying it's much easier to
follow the comments when they are provided by the actual code. That's it.
It's the usual way.
Powered by blists - more mailing lists