From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: "G Thomas, Rohan" <rohan.g.thomas@altera.com>
Cc: Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <Jose.Abreu@synopsys.com>,
Rohan G Thomas <rohan.g.thomas@intel.com>,
Boon Khai Ng <boon.khai.ng@altera.com>,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Matthew Gerlach <matthew.gerlach@altera.com>
Subject: Re: [PATCH net v3 2/3] net: stmmac: Consider Tx VLAN offload tag length for maxSDU
Date: Thu, 23 Oct 2025 11:59:21 +0100 [thread overview]
Message-ID: <aPoKiREmRurn-Mle@shell.armlinux.org.uk> (raw)
In-Reply-To: <0d3a8abe-773c-4859-9d6f-d08c118ce610@altera.com>
On Sat, Oct 18, 2025 at 07:20:03AM +0530, G Thomas, Rohan wrote:
> Hi Vadim,
>
> On 10/17/2025 5:51 PM, Vadim Fedorenko wrote:
> > On 17/10/2025 08:36, G Thomas, Rohan wrote:
> > > Hi All,
> > >
> > > On 10/17/2025 11:41 AM, Rohan G Thomas via B4 Relay wrote:
> > > > + sdu_len = skb->len;
> > > > /* Check if VLAN can be inserted by HW */
> > > > has_vlan = stmmac_vlan_insert(priv, skb, tx_q);
> > > > + if (has_vlan)
> > > > + sdu_len += VLAN_HLEN;
> > > > +
> > > > + if (priv->est && priv->est->enable &&
> > > > + priv->est->max_sdu[queue] &&
> > > > + skb->len > priv->est->max_sdu[queue]){
> > >
> > > I just noticed an issue with the reworked fix after sending the patch.
> > > The condition should be: sdu_len > priv->est->max_sdu[queue]
> > >
> > > I’ll send a corrected version, and will wait for any additional comments
> > > in the meantime.
> >
> > Well, even though it's a copy of original code, it would be good to
> > improve some formatting and add a space at the end of if statement to
> > make it look like 'if () {'>
>
> Thanks for pointing this out. I'll fix the formatting in the next version.
I suggest:
First patch - fix formatting.
Second patch - move the code.
We have a general rule that when code is moved, it should be moved with
no changes - otherwise it makes review much harder.
Thanks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-10-23 10:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 6:11 [PATCH net v3 0/3] net: stmmac: Fixes for stmmac Tx VLAN insert and EST Rohan G Thomas
2025-10-17 6:11 ` Rohan G Thomas via B4 Relay
2025-10-17 6:11 ` [PATCH net v3 1/3] net: stmmac: vlan: Disable 802.1AD tag insertion offload Rohan G Thomas
2025-10-17 6:11 ` Rohan G Thomas via B4 Relay
2025-10-17 12:42 ` Russell King (Oracle)
2025-10-18 1:56 ` G Thomas, Rohan
2025-10-23 3:31 ` G Thomas, Rohan
2025-10-23 10:54 ` Russell King (Oracle)
2025-10-24 3:03 ` G Thomas, Rohan
2025-10-17 6:11 ` [PATCH net v3 2/3] net: stmmac: Consider Tx VLAN offload tag length for maxSDU Rohan G Thomas
2025-10-17 6:11 ` Rohan G Thomas via B4 Relay
2025-10-17 7:36 ` G Thomas, Rohan
2025-10-17 12:21 ` Vadim Fedorenko
2025-10-18 1:50 ` G Thomas, Rohan
2025-10-23 10:59 ` Russell King (Oracle) [this message]
2025-10-23 16:03 ` G Thomas, Rohan
2025-10-17 12:44 ` Russell King (Oracle)
2025-10-18 2:06 ` G Thomas, Rohan
2025-10-23 10:58 ` Russell King (Oracle)
2025-10-17 17:16 ` kernel test robot
2025-10-27 9:03 ` G Thomas, Rohan
2025-10-17 6:11 ` [PATCH net v3 3/3] net: stmmac: est: Fix GCL bounds checks Rohan G Thomas
2025-10-17 6:11 ` Rohan G Thomas via B4 Relay
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=aPoKiREmRurn-Mle@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Jose.Abreu@synopsys.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=boon.khai.ng@altera.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=matthew.gerlach@altera.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rohan.g.thomas@altera.com \
--cc=rohan.g.thomas@intel.com \
--cc=vadim.fedorenko@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.