From: Ratheesh Kannoth <rkannoth@marvell.com>
To: "Jagielski, Jedrzej" <jedrzej.jagielski@intel.com>
Cc: "cjacob@marvell.com" <cjacob@marvell.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"hkelam@marvell.com" <hkelam@marvell.com>,
"jbrandeb@kernel.org" <jbrandeb@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"sgoutham@marvell.com" <sgoutham@marvell.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
Naveen Mamindlapalli <naveenm@marvell.com>
Subject: Re: [PATCH net] octeontx2-af: poll for TX link credits before link mode change
Date: Wed, 19 Aug 2026 15:00:06 +0530 [thread overview]
Message-ID: <aoV3nsNGhII1ukPt@rkannoth-OptiPlex-7090> (raw)
In-Reply-To: <PH0PR11MB5902FD7CDC98BEB8D8BFE356F0A52@PH0PR11MB5902.namprd11.prod.outlook.com>
On 2026-08-19 at 14:47:52, Jagielski, Jedrzej (jedrzej.jagielski@intel.com) wrote:
>
> if something is a clear for loop why make it complicated?
> again, not insisting - just asking
I really appreciate you taking the time to review this and share your
perspective. We generally aim to keep established code as is unless
there's a functional bug or clear readability issue, so we'll leave this
part as is for now.
next prev parent reply other threads:[~2026-08-19 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 3:36 [PATCH net] octeontx2-af: poll for TX link credits before link mode change Ratheesh Kannoth
2026-08-18 7:38 ` Jagielski, Jedrzej
2026-08-19 4:38 ` Ratheesh Kannoth
2026-08-19 9:17 ` Jagielski, Jedrzej
2026-08-19 9:30 ` Ratheesh Kannoth [this message]
2026-08-20 3:38 ` Ratheesh Kannoth
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=aoV3nsNGhII1ukPt@rkannoth-OptiPlex-7090 \
--to=rkannoth@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=cjacob@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkelam@marvell.com \
--cc=jbrandeb@kernel.org \
--cc=jedrzej.jagielski@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naveenm@marvell.com \
--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