From: "Karumanchi, Vineeth" <vineeth@amd.com>
To: Nicolai Buchwitz <nb@tipi-net.de>,
Vineeth Karumanchi <vineeth.karumanchi@amd.com>
Cc: theo.lebrun@bootlin.com, conor.dooley@microchip.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, git@amd.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net: macb: configure ENST registers for all queues
Date: Mon, 27 Jul 2026 15:31:28 +0530 [thread overview]
Message-ID: <46f74c84-f07a-4f23-b72b-7af12838743e@amd.com> (raw)
In-Reply-To: <49ccdd6682366239fef37bcfd99a908c@tipi-net.de>
Hi Nicolai,
On 7/25/2026 1:27 AM, Nicolai Buchwitz wrote:
<..>
>> Key changes:
>> - Drop queue_id from struct macb_queue_enst_config
>> - Allocate enst_queue[] based on bp->num_queues instead of
>> conf->num_entries
>> - Index enst_queue[] directly with the queue number
>> - Program ENST registers for all queues
>>
>> Fixes: 89934dbf169e ("net: macb: Add TAPRIO traffic scheduling support")
>
> In addition to what Théo already mentioned:
>
> The series targets net-next, but if this is a real bug fix it should
> probably be routed via net. The offending commit is in stable since v6.18.
Sure, I will split the patch series accordingly and submit the updated
versions to *net-next* and *net*.
Thanks
--
🙏 Vineeth
prev parent reply other threads:[~2026-07-27 10:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 4:32 [PATCH net-next 0/2] net: macb: fix ENST configuration for all queues Vineeth Karumanchi
2026-07-24 4:32 ` [PATCH net-next 1/2] net: macb: remove unused ENST Q0/Q1 time register defines Vineeth Karumanchi
2026-07-24 17:49 ` Théo Lebrun
2026-07-24 19:40 ` Nicolai Buchwitz
2026-07-24 4:32 ` [PATCH net-next 2/2] net: macb: configure ENST registers for all queues Vineeth Karumanchi
2026-07-24 18:06 ` Théo Lebrun
2026-07-27 5:32 ` Karumanchi, Vineeth
2026-07-27 12:05 ` Théo Lebrun
2026-07-27 12:52 ` Théo Lebrun
2026-07-24 19:57 ` Nicolai Buchwitz
2026-07-27 10:01 ` 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=46f74c84-f07a-4f23-b72b-7af12838743e@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=nb@tipi-net.de \
--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