From: Sagar Cheluvegowda <sagar.cheluvegowda@oss.qualcomm.com>
To: netdev-bot+sashiko@kernel.org
Cc: maxime.chevallier@bootlin.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, lorenzo.bianconi@oss.qualcomm.com,
hongmei.xu@oss.qualcomm.com, abhishek.chauhan@oss.qualcomm.com,
sarosh.hasan@oss.qualcomm.com
Subject: Re: [PATCH net-next v4] net: stmmac: dwxgmac2: enable L2 split header support
Date: Mon, 2 Nov 2026 16:26:25 -0800 [thread overview]
Message-ID: <374c9df9-eb58-48eb-8447-b6340df37719@oss.qualcomm.com> (raw)
In-Reply-To: <32fc0379-0c45-4011-a7ce-795c44594b89@oss.qualcomm.com>
> Agreed. I will send the FD/LD handling in dwxgmac2_get_rx_header_len()
> as a separate patch to net with:
>
> Fixes: 96147375d49f ("net: stmmac: xgmac: Only get SPH header len if available")
>
> and rebase the L2 split header support on top of it for net-next.
Correction on this point: there is no user-visible bug in the current
code, so I won't be sending a net fix. On XGMAC the RX buffers are
sized so that a frame always fits in a single descriptor, so the
FD=1/LD=0 case where L34T is not valid is not hit today.
I will keep the FD/LD handling in v5 to follow the databook's "Header
Length Availability in RDES2" table, without describing it as a fix.
Regards,
Sagar
prev parent reply other threads:[~2026-11-03 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 22:12 Sagar Cheluvegowda
2026-10-19 22:29 ` netdev-bot+sashiko
2026-10-28 1:10 ` Sagar Cheluvegowda
2026-11-03 0:26 ` Sagar Cheluvegowda [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=374c9df9-eb58-48eb-8447-b6340df37719@oss.qualcomm.com \
--to=sagar.cheluvegowda@oss.qualcomm.com \
--cc=abhishek.chauhan@oss.qualcomm.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hongmei.xu@oss.qualcomm.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lorenzo.bianconi@oss.qualcomm.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sarosh.hasan@oss.qualcomm.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
all inboxes | Powered by JetHome®