[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f0075083-8a11-a2f4-a927-7cd5f255bde4@intel.com>
Date: Tue, 8 Nov 2022 09:08:47 +0100
From: "Wilczynski, Michal" <michal.wilczynski@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: <netdev@...r.kernel.org>, <alexandr.lobakin@...el.com>,
<jacob.e.keller@...el.com>, <jesse.brandeburg@...el.com>,
<przemyslaw.kitszel@...el.com>, <anthony.l.nguyen@...el.com>,
<ecree.xilinx@...il.com>, <jiri@...nulli.us>
Subject: Re: [PATCH net-next v9 0/9] Implement devlink-rate API and extend it
On 11/7/2022 7:31 PM, Jakub Kicinski wrote:
> On Mon, 7 Nov 2022 19:18:10 +0100 Wilczynski, Michal wrote:
>> I provided some documentation in v10 in ice.rst file.
>> Unfortunately there is no devlink-rate.rst as far as I can
>> tell and at some point we even discussed adding this with Edward,
>> but honestly I think this could be added in a separate patch
>> series to not unnecessarily prolong merging this.
> You can't reply to email and then immediately post a new version :/
> How am I supposed to have a conversation with you? Extremely annoying.
I'm sorry if you find this annoying, however I can't see any harm here ?
I fixed some legit issues that you've pointed in v9, wrote some
documentation and basically said, "I wrote some documentation in
the next patchset, is it enough ?". I think it's better to get feedback
for smaller commits faster, this way I send the updated patchset
quickly.
>
> I'm tossing v10 from patchwork, and v11 better come with the docs :/
I will however create a new devlink-rate.rst file if you insist.
BR,
MichaĆ
Powered by blists - more mailing lists