From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next] net: stmmac: fix dwmac4 transmit performance regression
Date: Sat, 17 Jan 2026 10:26:26 +0100 [thread overview]
Message-ID: <afbac1ba-43b4-4c0a-84fd-87866e954fa2@bootlin.com> (raw)
In-Reply-To: <aWrH-FAuWnqmbSaJ@shell.armlinux.org.uk>
> I really give up with when fixes should be added or not, because it
> seems quite random when it's needed and when it isn't.
>
> And no, don't quote the stable-kernel-rules nonsense that is
> meaningless ot stable kernel people, when they use AI to analyse
> commits and pick stuff completely randomly.
The rule I'm following is the one in the netdev-maintainer doc, that says:
'for fixes the Fixes: tag is required, regardless of the tree'
>
>> It would also have been nice to be in CC, I spent some time on the bisect...
>
> I thought you were, but I see now it was a different Maxime!
Bah, no worries :)
Seems we have a bunch of french people with similar names working with
st platforms or stmmac on a regular basis, I understand the confusion :
Maxime Coquelin
Maxime Chevallier
Gatien Chevallier
Anyways, thanks for the quick fix on that !
Maxime
next prev parent reply other threads:[~2026-01-17 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 0:49 [PATCH net-next] net: stmmac: fix dwmac4 transmit performance regression Russell King (Oracle)
2026-01-16 7:42 ` Maxime Chevallier
2026-01-16 23:21 ` Russell King (Oracle)
2026-01-17 9:26 ` Maxime Chevallier [this message]
2026-01-19 14:19 ` patchwork-bot+netdevbpf
2026-03-13 15:03 ` Georg Gottleuber
2026-03-13 16:35 ` Russell King (Oracle)
2026-03-13 18:39 ` Russell King (Oracle)
2026-03-16 10:51 ` Georg Gottleuber
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=afbac1ba-43b4-4c0a-84fd-87866e954fa2@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox