From: Vladimir Oltean <olteanv@gmail.com>
To: Kurt Kanzenbach <kurt@linutronix.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Richard Cochran <richardcochran@gmail.com>,
Kamil Alkhouri <kamil.alkhouri@hs-offenburg.de>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/4] net: dsa: hellcreek: Fix insertion of static FDB entries
Date: Tue, 14 Dec 2021 22:53:40 +0200 [thread overview]
Message-ID: <20211214205340.mm5xgvkphk4m3y4e@skbuf> (raw)
In-Reply-To: <20211214134508.57806-2-kurt@linutronix.de>
On Tue, Dec 14, 2021 at 02:45:05PM +0100, Kurt Kanzenbach wrote:
> The insertion of static FDB entries ignores the pass_blocked bit. That bit is
> evaluated with regards to STP. Add the missing functionality.
>
> Fixes: e4b27ebc780f ("net: dsa: Add DSA driver for Hirschmann Hellcreek switches")
> Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de>
> ---
Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
next prev parent reply other threads:[~2021-12-14 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 13:45 [PATCH net-next v2 0/4] net: dsa: hellcreek: Fix handling of MGMT protocols Kurt Kanzenbach
2021-12-14 13:45 ` [PATCH net-next v2 1/4] net: dsa: hellcreek: Fix insertion of static FDB entries Kurt Kanzenbach
2021-12-14 20:53 ` Vladimir Oltean [this message]
2021-12-14 13:45 ` [PATCH net-next v2 2/4] net: dsa: hellcreek: Add STP forwarding rule Kurt Kanzenbach
2021-12-14 20:55 ` Vladimir Oltean
2021-12-14 13:45 ` [PATCH net-next v2 3/4] net: dsa: hellcreek: Allow PTP P2P measurements on blocked ports Kurt Kanzenbach
2021-12-14 20:54 ` Vladimir Oltean
2021-12-14 13:45 ` [PATCH net-next v2 4/4] net: dsa: hellcreek: Add missing PTP via UDP rules Kurt Kanzenbach
2021-12-14 20:09 ` [PATCH net-next v2 0/4] net: dsa: hellcreek: Fix handling of MGMT protocols Richard Cochran
2021-12-15 3:00 ` patchwork-bot+netdevbpf
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=20211214205340.mm5xgvkphk4m3y4e@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kamil.alkhouri@hs-offenburg.de \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--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