From: Meghana Malladi <m-malladi@ti.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <diogo.ivo@siemens.com>, <haokexin@gmail.com>,
<philippe.schenker@impulsing.ch>, <devnexen@gmail.com>,
<horms@kernel.org>, <jacob.e.keller@intel.com>,
<pabeni@redhat.com>, <edumazet@kernel.org>, <davem@davemloft.net>,
<andrew+netdev@lunn.ch>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>,
Vignesh Raghavendra <vigneshr@ti.com>, <danishanwar@ti.com>
Subject: Re: [PATCH net v3 RESEND 0/3] Fix switch mode for offload and non-offload cases
Date: Sat, 21 Nov 2026 20:37:34 +0530 [thread overview]
Message-ID: <c2167ce6-45da-4868-9212-db4811282e66@ti.com> (raw)
In-Reply-To: <20261119164407.1d2b3fa2@kernel.org>
Hi Jakub,
On 11/20/26 06:14, Jakub Kicinski wrote:
> On Thu, 12 Nov 2026 15:51:37 +0530 Meghana Malladi wrote:
>> v2: https://lore.kernel.org/all/20261027131732.3411403-1-m-malladi@ti.com/
>
> What changed in v3? When was v3 posted (since this is a repost?)
I first posted v3 on November 10 and resent the full series on
November 12. Here's the original cover letter:
https://lore.kernel.org/all/20261110122700.1849634-1-m-malladi@ti.com/
I reposted because I lately realized patch 3/3 was missing (could me
mail server glitch)
I included the v2-to-v3 changes in the individual patch notes. Here's
the summary for the series:
* Patch 1/3 adds a TX timestamp cleanup fix so reserved ERR_PTR(-EBUSY)
slots are cleared without attempting to free them as skbs.
* Patch 2/3 changes the R30 race fix to stop and restart phylib around
the PRU firmware restart, so emac_adjust_link() cannot issue R30
commands while the firmware is stopped.
* Patch 3/3 records the UC/MC flooding flags before issuing the firmware
commands and restores the flooding state after firmware restarts on
bridge and HSR unlink. It also carries the NULL emac check from v2.
> You are expected to reply to the sashiko review, even if just
> to confirm that it's correct.
Yes, got it. Some series specifically ask for it and some don't. So it
slipped my mind while posting. I will keep that in mind for my upcoming
patches.
Thanks,
Meghana
prev parent reply other threads:[~2026-11-21 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 10:21 [PATCH net v3 RESEND 0/3] Fix switch mode for offload and non-offload cases Meghana Malladi
2026-11-12 10:21 ` [PATCH net v3 RESEND 1/3] net: ti: icssg-prueth: Fix TX timestamp cleanup crash Meghana Malladi
2026-11-16 13:54 ` netdev-bot+sashiko
2026-11-12 10:21 ` [PATCH net v3 RESEND 2/3] net: ti: icssg-prueth: Fix phylib stop/start in emac_restart Meghana Malladi
2026-11-16 13:54 ` netdev-bot+sashiko
2026-11-12 10:21 ` [PATCH net v3 RESEND 3/3] net: ti: icssg-prueth: Fix bridge port_vlan and flooding state Meghana Malladi
2026-11-16 13:54 ` netdev-bot+sashiko
2026-11-12 10:26 ` [PATCH net v3 RESEND 0/3] Fix switch mode for offload and non-offload cases netdev-bot+sinfo
2026-11-20 0:44 ` Jakub Kicinski
2026-11-21 15:07 ` 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=c2167ce6-45da-4868-9212-db4811282e66@ti.com \
--to=m-malladi@ti.com \
--cc=andrew+netdev@lunn.ch \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=devnexen@gmail.com \
--cc=diogo.ivo@siemens.com \
--cc=edumazet@kernel.org \
--cc=haokexin@gmail.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=philippe.schenker@impulsing.ch \
--cc=vigneshr@ti.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