From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org (open list),
stable@vger.kernel.org, gregkh@linuxfoundation.org,
sashal@kernel.org
Subject: [PATCH stable 0/6] net: dsa: b53: Correct learning for standalone ports
Date: Tue, 16 Mar 2021 17:35:43 -0700 [thread overview]
Message-ID: <20210317003549.3964522-1-f.fainelli@gmail.com> (raw)
Hi Greg, Sasha, Jaakub and David,
This patch series contains backports for a change that recently made it
upstream as f9b3827ee66cfcf297d0acd6ecf33653a5f297ef ("net: dsa: b53:
Support setting learning on port") however that commit depends on
infrastructure that landed in v5.12-rc1.
The way this was fixed in the netdev group's net tree is slightly
different from how it should be backported to stable trees which is why
you will find a patch for each branch in the thread started by this
cover letter. The commit used as a Fixes: base dates back from when the
driver was first introduced into the tree since this should have been
fixed from day one ideally.
Let me know if this does not apply for some reason. The changes from 4.9
through 4.19 are nearly identical and then from 5.4 through 5.11 are
about the same.
Thank you very much!
--
2.25.1
next reply other threads:[~2021-03-17 0:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 0:35 Florian Fainelli [this message]
2021-03-17 0:35 ` [PATCH stable 4.9] " Florian Fainelli
2021-03-17 0:35 ` [PATCH stable 4.14] " Florian Fainelli
2021-03-17 0:35 ` [PATCH stable 4.19] " Florian Fainelli
2021-03-17 0:35 ` [PATCH stable 5.4] " Florian Fainelli
2021-03-17 0:35 ` [PATCH stable 5.10] " Florian Fainelli
2021-03-17 0:35 ` [PATCH stable 5.11] " Florian Fainelli
2021-03-17 14:14 ` [PATCH stable 0/6] " Vladimir Oltean
2021-03-19 10:48 ` Greg KH
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=20210317003549.3964522-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vivien.didelot@gmail.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®