From: "Karumanchi, Vineeth" <vineeth@amd.com>
To: Jakub Kicinski <kuba@kernel.org>, vineeth.karumanchi@amd.com
Cc: theo.lebrun@bootlin.com, conor.dooley@microchip.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, git@amd.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: macb: configure ENST registers for all queues
Date: Tue, 1 Sep 2026 14:50:38 +0530 [thread overview]
Message-ID: <97659f05-eb58-4c90-96b2-59d8d8c9830b@amd.com> (raw)
In-Reply-To: <4c719349-132b-4dcd-b332-a84d3a92b7df@amd.com>
Hi Jakub,
On 8/11/2026 3:47 PM, Karumanchi, Vineeth wrote:
> Hi Jakub,
>
> On 8/11/2026 6:48 AM, Jakub Kicinski wrote:
>> On Thu, 6 Aug 2026 09:25:57 -0700 Jakub Kicinski wrote:
>>> This is an AI-generated review of your patch. The human sending this
>>> email says "What's the expectation for the other queues?"
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> Highlighting this (human) question in case it was missed in the wall
>> of (AI) text.
>
> Sorry, I missed your comment.
>
> I verified the behavior both with and without this patch. In both cases,
> the other queues remain disabled, and all traffic is transmitted only
> through the ENST enabled queues. which is the expected behavior.
>
Just following up on this patch. I hope the explanation above clarifies
the expected behavior. Please let me know if anything else needs to be
addressed.
Thanks,
--
🙏 Vineeth
prev parent reply other threads:[~2026-09-01 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 4:42 [PATCH net v2] net: macb: configure ENST registers for all queues Vineeth Karumanchi
2026-08-05 13:14 ` Théo Lebrun
2026-08-06 16:25 ` Jakub Kicinski
2026-08-11 1:18 ` Jakub Kicinski
2026-08-11 10:17 ` Karumanchi, Vineeth
2026-09-01 9:20 ` Karumanchi, Vineeth [this message]
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=97659f05-eb58-4c90-96b2-59d8d8c9830b@amd.com \
--to=vineeth@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=git@amd.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=theo.lebrun@bootlin.com \
--cc=vineeth.karumanchi@amd.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