From: Greg KH <gregkh@linuxfoundation.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev@vger.kernel.org,
Florian Fainelli <florian.fainelli@broadcom.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
open list <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, olteanv@gmail.com, sashal@kernel.org
Subject: Re: [PATCH stable 0/8] net: dsa: b53: Correct learning for standalone ports
Date: Thu, 25 Feb 2021 09:15:58 +0100 [thread overview]
Message-ID: <YDdcvkQQoAs2yc3C@kroah.com> (raw)
In-Reply-To: <20210225010853.946338-1-f.fainelli@gmail.com>
On Wed, Feb 24, 2021 at 05:08:53PM -0800, Florian Fainelli wrote:
> From: Florian Fainelli <florian.fainelli@broadcom.com>
>
> Hi Greg, Sasha, Jaakub and David,
>
> This patch series contains backports for a change that recently made it
> upstream as:
>
> commit f3f9be9c58085d11f4448ec199bf49dc2f9b7fb9
> Merge: 18755e270666 f9b3827ee66c
> Author: Jakub Kicinski <kuba@kernel.org>
> Date: Tue Feb 23 12:23:06 2021 -0800
>
> Merge branch 'net-dsa-learning-fixes-for-b53-bcm_sf2'
That is a merge commit, not a "real" commit.
What is the upstream git commit id for this?
> 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.
>
> 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.
Thanks for the backports, but I still need a real git id to match these
up with :)
greg k-h
next prev parent reply other threads:[~2021-02-25 8:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 1:08 [PATCH stable 0/8] net: dsa: b53: Correct learning for standalone ports Florian Fainelli
2021-02-25 1:09 ` [PATCH stable-4.9.y] " Florian Fainelli
2021-02-25 1:09 ` [PATCH stable-4.14.y] " Florian Fainelli
2021-02-25 1:09 ` [PATCH stable-4.19.y] " Florian Fainelli
2021-02-25 1:09 ` [PATCH stable-5.4.y] " Florian Fainelli
2021-02-25 1:09 ` [PATCH stable-5.8.y] " Florian Fainelli
2021-02-25 1:09 ` [PATCH stable-5.9.y] " Florian Fainelli
2021-02-25 8:16 ` Greg KH
2021-02-25 1:09 ` [PATCH stable-5.10.y] " Florian Fainelli
2021-02-25 1:09 ` [PATCH stable-5.11.y] " Florian Fainelli
2021-02-25 8:15 ` Greg KH [this message]
2021-02-25 16:53 ` [PATCH stable 0/8] " Florian Fainelli
2021-02-25 17:11 ` Greg KH
2021-02-25 18:31 ` Florian Fainelli
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=YDdcvkQQoAs2yc3C@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--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 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.