From: Meghana Malladi <m-malladi@ti•com>
To: Simon Horman <horms@kernel•org>
Cc: <liuhangbin@gmail•com>, <haokexin@gmail•com>,
<vadim.fedorenko@linux•dev>, <devnexen@gmail•com>,
<jacob.e.keller@intel•com>, <arnd@arndb•de>, <afd@ti•com>,
<basharath@couthit•com>, <parvathi@couthit•com>,
<vladimir.oltean@nxp•com>, <rogerq@kernel•org>,
<danishanwar@ti•com>, <pabeni@redhat•com>, <kuba@kernel•org>,
<edumazet@google•com>, <davem@davemloft•net>,
<andrew+netdev@lunn•ch>, <linux-arm-kernel@lists•infradead.org>,
<netdev@vger•kernel.org>, <linux-kernel@vger•kernel.org>,
<srk@ti•com>, Vignesh Raghavendra <vigneshr@ti•com>
Subject: Re: [PATCH net-next v6 0/2] Add Frame Preemption MAC Merge support for ICSSG
Date: Thu, 4 Jun 2026 19:09:41 +0530 [thread overview]
Message-ID: <86d2c8b6-4240-4ac7-aca1-915d330cddf4@ti.com> (raw)
In-Reply-To: <20260527115755.GK2256768@horms.kernel.org>
Hi Simon,
On 5/27/26 17:27, Simon Horman wrote:
> On Mon, May 25, 2026 at 11:56:58PM +0530, Meghana Malladi wrote:
>> This patch series adds QoS support to the ICSSG PRUETH driver.
>> The first patch implements mqprio qdisc handling and TC offload hooks
>> so userspace can request TC mappings and queue counts.
>>
>> It also integrates a driver-side mechanism to program the firmware
>> with the IET/FPE preemption mask and to kick the firmware verify state
>> machine when frame preemption is enabled. The second patch adds ethtool
>> perations for the MAC Merge (Frame Preemption) sublayer, exposing .get_mm,
>> .set_mm and .get_mm_stats so admins can view and change MAC Merge
>> parameters and retrieve preemption statistics.
>>
>> v5: https://lore.kernel.org/all/20260430111723.497113-1-m-malladi@ti.com/
>>
>> MD Danish Anwar (2):
>> net: ti: icssg-prueth: Add Frame Preemption MAC Merge support
>> net: ti: icssg-prueth: Add ethtool ops for Frame Preemption MAC Merge
>
> Hi Meghana and MD,
>
> There is another round of AI-generated reviews for this patch-set available at
> https://netdev-ai.bots.linux.dev/ and https://sashiko.dev/
>
> I would appreciate it if you could look over them and address any
> issues that are either introduced by this patch-set, or directly
> impact it.
>
Yeah I am working on it, though some of them seem to be false positives,
some actually made sense. Hopefully I will fix all of them without
introducing anything new in my next version.
> I would not suggest expanding this patchset to address any other
> pre-existing issues, but rather address them separately as appropriate.
prev parent reply other threads:[~2026-06-04 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 18:26 [PATCH net-next v6 0/2] Add Frame Preemption MAC Merge support for ICSSG Meghana Malladi
2026-05-25 18:26 ` [PATCH net-next v6 1/2] net: ti: icssg-prueth: Add Frame Preemption MAC Merge support Meghana Malladi
2026-05-25 19:18 ` Maxime Chevallier
2026-05-25 19:46 ` Andrew Lunn
2026-06-04 13:37 ` Meghana Malladi
2026-06-04 13:37 ` Meghana Malladi
2026-05-25 18:27 ` [PATCH net-next v6 2/2] net: ti: icssg-prueth: Add ethtool ops for Frame Preemption MAC Merge Meghana Malladi
2026-05-25 19:35 ` Maxime Chevallier
2026-06-04 13:45 ` Meghana Malladi
2026-05-27 11:57 ` [PATCH net-next v6 0/2] Add Frame Preemption MAC Merge support for ICSSG Simon Horman
2026-06-04 13:39 ` Meghana Malladi [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=86d2c8b6-4240-4ac7-aca1-915d330cddf4@ti.com \
--to=m-malladi@ti$(echo .)com \
--cc=afd@ti$(echo .)com \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=arnd@arndb$(echo .)de \
--cc=basharath@couthit$(echo .)com \
--cc=danishanwar@ti$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=devnexen@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=haokexin@gmail$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=jacob.e.keller@intel$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=liuhangbin@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=parvathi@couthit$(echo .)com \
--cc=rogerq@kernel$(echo .)org \
--cc=srk@ti$(echo .)com \
--cc=vadim.fedorenko@linux$(echo .)dev \
--cc=vigneshr@ti$(echo .)com \
--cc=vladimir.oltean@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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