From: Jakub Kicinski <kuba@kernel.org>
To: Richard Tresidder <rtresidd@electromag.com.au>
Cc: Romain Gantois <romain.gantois@bootlin.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, "G Thomas,
Rohan" <rohan.g.thomas@intel.com>
Subject: Re: [PATCH net v6] net: stmmac: Prevent DSA tags from breaking COE
Date: Thu, 1 Feb 2024 07:05:51 -0800 [thread overview]
Message-ID: <20240201070551.7147faee@kernel.org> (raw)
In-Reply-To: <b757b71b-2460-48fe-a163-f7ddfb982725@electromag.com.au>
On Thu, 1 Feb 2024 17:38:07 +0800 Richard Tresidder wrote:
> Thanks for your work on this patch.
> I was wondering if this would make it's way onto the lts kernel branch at some point?
> I think this patch relies on at least a few others that don't appear to have been ported across either.
> eg: at least 2023-09-18 Rohan G Thomas net: stmmac: Tx coe sw fallback
>
> Just looking at having to abandon the 6.6 lts kernel I'm basing things on as we require this patchset to get our network system working.
> Again much appreciated!
Hm, it may have gotten missed because of the double space in:
Cc: <stable@vger.kernel.org>
double check if it's present in the stable tree and if not please
request the backport, the info you need to provide is somewhere
in kernel doc's process section.
next prev parent reply other threads:[~2024-02-01 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 12:19 [PATCH net v6] net: stmmac: Prevent DSA tags from breaking COE Romain Gantois
2024-01-16 20:56 ` Florian Fainelli
2024-01-17 10:10 ` patchwork-bot+netdevbpf
2024-02-01 9:38 ` Richard Tresidder
2024-02-01 15:05 ` Jakub Kicinski [this message]
2024-02-02 3:10 ` Richard Tresidder
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=20240201070551.7147faee@kernel.org \
--to=kuba@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rohan.g.thomas@intel.com \
--cc=romain.gantois@bootlin.com \
--cc=rtresidd@electromag.com.au \
/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;
as well as URLs for NNTP newsgroup(s).