[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250717064554.3e4d9993@kernel.org>
Date: Thu, 17 Jul 2025 06:45:54 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Krishna Kumar <krikku@...il.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
tom@...bertland.com, pabeni@...hat.com, horms@...nel.org, sdf@...ichev.me,
kuniyu@...gle.com, ahmed.zaki@...el.com, aleksander.lobakin@...el.com,
atenart@...nel.org, jdamato@...tly.com, krishna.ku@...pkart.com
Subject: Re: [PATCH v3 net-next 0/2] net: RPS table overwrite prevention and
flow_id caching
On Thu, 17 Jul 2025 13:26:56 +0530 Krishna Kumar wrote:
> This series splits the previous RPS patch [1] into two patches for
> net-next following reviewer feedback. It also addresses a kernel test
> robot warning by ensuring rps_flow_is_active() is defined only when
> aRFS is enabled. I tested v3 with four builds and reboots: two for
> [PATCH 1/2] with aRFS enabled/disabled, and two for [PATCH 2/2].
Quoting documentation:
Resending after review
~~~~~~~~~~~~~~~~~~~~~~
[...]
The new version of patches should be posted as a separate thread,
not as a reply to the previous posting. Change log should include a link
to the previous posting (see :ref:`Changes requested`).
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#resending-after-review
Powered by blists - more mailing lists