From: Ratheesh Kannoth <rkannoth@marvell.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<sgoutham@marvell.com>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>,
<andrew+netdev@lunn.ch>
Subject: Re: [PATCH net-next v9 00/13] NPC HW block support for cn20k
Date: Wed, 25 Feb 2026 07:26:47 +0530 [thread overview]
Message-ID: <aZ5W35hJWsU8btAN@rkannoth-OptiPlex-7090> (raw)
In-Reply-To: <20260224103537.4eed8e8b@kernel.org>
On 2026-02-25 at 00:05:37, Jakub Kicinski (kuba@kernel.org) wrote:
> On Tue, 24 Feb 2026 13:29:56 +0530 Ratheesh Kannoth wrote:
> > v8 -> v9: Addressed Jakub comments.
> > https://lore.kernel.org/netdev/20260204182428.05a77b13@kernel.org/
>
> v8 was 20 days ago. You replied to the review comments _today_ and then
> immediately posted v9. This is very frustrating, because corrections
> I suggested in the reply to v8 obviously can't be part of v9. Making v9
> pretty much useless. If you can't follow common sense rules of
> engagement with the community we will not merge any of your code.
I understand your frustration, and I apologize for posting v9 immediately
after replying to the v8 review comments. My intention was to keep the
process moving forward, as new AI generated review comments are generated each time.
I had asked the same question in v7
(https://lore.kernel.org/netdev/20260129083339.264386-12-rkannoth@marvell.com/T/#m0681b88b55f80b0f58fc1e6e9be2220220111224).
But I see now that doing so prevented your latest suggestions from being incorporated and disrupted the expected
review workflow. That was not my intent. I appreciate the time and effort you put into reviewing the patches,
and I certainly do not want to undermine that process.
Going forward, I will wait for feedback after replying to review comments before posting a new version,
to ensure that all suggested corrections are properly addressed. If there are additional changes you would like
included beyond what was already discussed, I am happy to incorporate them in the next revision.
Thank you again for the review and for your guidance on community expectations.
next prev parent reply other threads:[~2026-02-25 1:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 7:59 Ratheesh Kannoth
2026-02-24 7:59 ` [PATCH net-next v9 01/13] octeontx2-af: npc: cn20k: Index management Ratheesh Kannoth
2026-02-24 7:59 ` [PATCH net-next v9 02/13] octeontx2-af: npc: cn20k: KPM profile changes Ratheesh Kannoth
2026-02-24 7:59 ` [PATCH net-next v9 03/13] octeontx2-af: npc: cn20k: Add default profile Ratheesh Kannoth
2026-02-24 8:00 ` [PATCH net-next v9 04/13] octeontx2-af: npc: cn20k: MKEX profile support Ratheesh Kannoth
2026-02-24 8:00 ` [PATCH net-next v9 05/13] octeontx2-af: npc: cn20k: Allocate default MCAM indexes Ratheesh Kannoth
2026-02-24 8:00 ` [PATCH net-next v9 06/13] octeontx2-af: npc: cn20k: Use common APIs Ratheesh Kannoth
2026-02-24 8:00 ` [PATCH net-next v9 07/13] octeontx2-af: npc: cn20k: Prepare for new SoC Ratheesh Kannoth
2026-02-24 8:00 ` [PATCH net-next v9 08/13] octeontx2-af: npc: cn20k: Add new mailboxes for CN20K silicon Ratheesh Kannoth
2026-02-24 8:00 ` [PATCH net-next v9 09/13] octeontx2-af: npc: cn20k: virtual index support Ratheesh Kannoth
2026-02-24 8:00 ` [PATCH net-next v9 10/13] octeontx2-af: npc: cn20k: Allocate MCAM entry for flow installation Ratheesh Kannoth
2026-02-24 8:00 ` [PATCH net-next v9 11/13] octeontx2-pf: cn20k: Add TC rules support Ratheesh Kannoth
2026-02-24 8:00 ` [PATCH net-next v9 12/13] octeontx2-af: npc: cn20k: add debugfs support Ratheesh Kannoth
2026-02-24 8:00 ` [PATCH net-next v9 13/13] octeontx2-af: npc: Use common structures Ratheesh Kannoth
2026-02-24 18:35 ` [PATCH net-next v9 00/13] NPC HW block support for cn20k Jakub Kicinski
2026-02-25 1:56 ` Ratheesh Kannoth [this message]
2026-02-28 18:50 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aZ5W35hJWsU8btAN@rkannoth-OptiPlex-7090 \
--to=rkannoth@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgoutham@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®