From: patchwork-bot+netdevbpf@kernel.org
To: Lorenzo Bianconi <lorenzo.bianconi@oss.qualcomm.com>
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, Jose.Abreu@synopsys.com,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net] net: stmmac: reconfigure RX packet parser table in stmmac_hw_setup() after reset
Date: Thu, 03 Sep 2026 09:50:09 +0000 [thread overview]
Message-ID: <178842900914.3234406.11176564790633654802.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260831-stmmac_tc_cls32_reconfigure-v1-1-21cb459e64ae@oss.qualcomm.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 31 Aug 2026 19:06:38 +0200 you wrote:
> The core software reset issued in stmmac_init_dma_engine() during
> ndo_open() callback clears the MTL RX packet parser registers, but
> stmmac_rxp_config() is only invoked from the cls_u32 add/delete paths.
> After an ifdown/ifup cycle the hardware therefore runs with the default
> all-pass table while priv->tc_entries still reports the filters as
> installed. Re-apply the RX packet parser table from priv->tc_entries in
> stmmac_hw_setup(), right after the software reset, so the filters are
> restored when the interface is brought up again.
>
> [...]
Here is the summary with links:
- [net] net: stmmac: reconfigure RX packet parser table in stmmac_hw_setup() after reset
https://git.kernel.org/netdev/net/c/6b8fed2675fb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-03 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 17:06 [PATCH net] net: stmmac: reconfigure RX packet parser table in stmmac_hw_setup() after reset Lorenzo Bianconi
2026-09-03 9:50 ` patchwork-bot+netdevbpf [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=178842900914.3234406.11176564790633654802.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Jose.Abreu@synopsys.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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@vger.kernel.org \
--cc=pabeni@redhat.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 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.