[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210723055626.GA32126@lst.de>
Date: Fri, 23 Jul 2021 07:56:26 +0200
From: Christoph Hellwig <hch@....de>
To: Boris Pismenny <borisp@...dia.com>
Cc: dsahern@...il.com, kuba@...nel.org, davem@...emloft.net,
saeedm@...dia.com, hch@....de, sagi@...mberg.me, axboe@...com,
kbusch@...nel.org, viro@...iv.linux.org.uk, edumazet@...gle.com,
smalin@...vell.com, boris.pismenny@...il.com,
linux-nvme@...ts.infradead.org, netdev@...r.kernel.org,
benishay@...dia.com, ogerlitz@...dia.com, yorayz@...dia.com,
Boris Pismenny <borisp@...lanox.com>
Subject: Re: [PATCH v5 net-next 00/36] nvme-tcp receive and tarnsmit
offloads
On Thu, Jul 22, 2021 at 02:02:49PM +0300, Boris Pismenny wrote:
> From: Boris Pismenny <borisp@...lanox.com>
>
> Changes since v4:
> =========================================
Explaining what the series does should go before the changelog.
> * Add transmit offload patches
But to be honest, the previous one was already mostly unreviewable,
but this is now far beyond this. Please try to get anything that
is generally useful first in smaller series and the come back with
a somewhat reviewable series. That also means that at least for the
code I care about (nvme) the patches should be grouped together,
and actually provide meaningful functionality in each patch. Right
now even trying to understand what you add to the nvme code requires
me to jump all over a gigantic series.
Powered by blists - more mailing lists