From: Sasha Levin <sashal@kernel.org>
To: DENG Qingfang <dqfext@gmail.com>
Cc: stable@vger.kernel.org, Sean Wang <sean.wang@mediatek.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Matthias Brugger <matthias.bgg@gmail.com>,
"open list:MEDIATEK SWITCH DRIVER" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH 4.19.y] net: dsa: mt7530: disable learning on standalone ports
Date: Tue, 24 Aug 2021 11:29:27 -0400 [thread overview]
Message-ID: <YSUQV3jhfbhbf5Ct@sashalap> (raw)
In-Reply-To: <20210824055509.1316124-1-dqfext@gmail.com>
On Tue, Aug 24, 2021 at 01:55:08PM +0800, DENG Qingfang wrote:
>This is a partial backport of commit 5a30833b9a16f8d1aa15de06636f9317ca51f9df
>("net: dsa: mt7530: support MDB and bridge flag operations") upstream.
>
>Make sure that the standalone ports start up with learning disabled.
What's the reasoning behind:
1. Backporting this patch?
2. A partial backport of this patch?
--
Thanks,
Sasha
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: DENG Qingfang <dqfext@gmail.com>
Cc: stable@vger.kernel.org, Sean Wang <sean.wang@mediatek.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Matthias Brugger <matthias.bgg@gmail.com>,
"open list:MEDIATEK SWITCH DRIVER" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH 4.19.y] net: dsa: mt7530: disable learning on standalone ports
Date: Tue, 24 Aug 2021 11:29:27 -0400 [thread overview]
Message-ID: <YSUQV3jhfbhbf5Ct@sashalap> (raw)
In-Reply-To: <20210824055509.1316124-1-dqfext@gmail.com>
On Tue, Aug 24, 2021 at 01:55:08PM +0800, DENG Qingfang wrote:
>This is a partial backport of commit 5a30833b9a16f8d1aa15de06636f9317ca51f9df
>("net: dsa: mt7530: support MDB and bridge flag operations") upstream.
>
>Make sure that the standalone ports start up with learning disabled.
What's the reasoning behind:
1. Backporting this patch?
2. A partial backport of this patch?
--
Thanks,
Sasha
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: DENG Qingfang <dqfext@gmail.com>
Cc: stable@vger.kernel.org, Sean Wang <sean.wang@mediatek.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Matthias Brugger <matthias.bgg@gmail.com>,
"open list:MEDIATEK SWITCH DRIVER" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH 4.19.y] net: dsa: mt7530: disable learning on standalone ports
Date: Tue, 24 Aug 2021 11:29:27 -0400 [thread overview]
Message-ID: <YSUQV3jhfbhbf5Ct@sashalap> (raw)
In-Reply-To: <20210824055509.1316124-1-dqfext@gmail.com>
On Tue, Aug 24, 2021 at 01:55:08PM +0800, DENG Qingfang wrote:
>This is a partial backport of commit 5a30833b9a16f8d1aa15de06636f9317ca51f9df
>("net: dsa: mt7530: support MDB and bridge flag operations") upstream.
>
>Make sure that the standalone ports start up with learning disabled.
What's the reasoning behind:
1. Backporting this patch?
2. A partial backport of this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2021-08-24 15:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 5:55 [PATCH 4.19.y] net: dsa: mt7530: disable learning on standalone ports DENG Qingfang
2021-08-24 5:55 ` DENG Qingfang
2021-08-24 5:55 ` DENG Qingfang
2021-08-24 15:29 ` Sasha Levin [this message]
2021-08-24 15:29 ` Sasha Levin
2021-08-24 15:29 ` Sasha Levin
2021-08-24 15:57 ` DENG Qingfang
2021-08-24 15:57 ` DENG Qingfang
2021-08-24 15:57 ` DENG Qingfang
2021-08-27 10:19 ` Greg KH
2021-08-27 10:19 ` Greg KH
2021-08-27 10:19 ` Greg KH
2021-09-02 5:36 ` DENG Qingfang
2021-09-02 5:36 ` DENG Qingfang
2021-09-02 5:36 ` DENG Qingfang
2021-09-02 5:58 ` Greg KH
2021-09-02 5:58 ` Greg KH
2021-09-02 5:58 ` Greg KH
2021-09-03 9:14 ` DENG Qingfang
2021-09-03 9:14 ` DENG Qingfang
2021-09-03 9:14 ` DENG Qingfang
2021-09-07 15:18 ` Greg KH
2021-09-07 15:18 ` Greg KH
2021-09-07 15:18 ` 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=YSUQV3jhfbhbf5Ct@sashalap \
--to=sashal@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sean.wang@mediatek.com \
--cc=stable@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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.