From: Andrew Lunn <andrew@lunn.ch>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
Network Development <netdev@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>
Subject: Re: vlan_filtering=1 breaks all traffic
Date: Tue, 8 Dec 2020 03:22:23 +0100 [thread overview]
Message-ID: <20201208022223.GF2475764@lunn.ch> (raw)
In-Reply-To: <20201207201527.nbo4jz5bga26celo@skbuf>
On Mon, Dec 07, 2020 at 08:15:28PM +0000, Vladimir Oltean wrote:
> On Mon, Dec 07, 2020 at 08:43:18PM +0100, Rasmus Villemoes wrote:
> > # uname -a
> > Linux (none) 5.10.0-rc7-00035-g66d777e1729d #194 Mon Dec 7 16:00:30 CET
> > 2020 ppc GNU/Linux
> > # devlink dev
> > mdio_bus/mdio@e0102120:10
> > # mv88e6xxx_dump --device mdio_bus/mdio@e0102120:10 --vtu
> > VTU:
> > Error: devlink: The requested region does not exist.
> > devlink answers: Invalid argument
> > Unable to snapshot vtu
VTU dumping is new. It is in net-next, but not 5.10-rc7. atu, global1
and global2 are part for 5.10-rc7.
Andrew
prev parent reply other threads:[~2020-12-08 2:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 14:30 warnings from MTU setting on switch ports Rasmus Villemoes
2020-11-30 16:04 ` Vladimir Oltean
2020-11-30 22:13 ` Rasmus Villemoes
2020-11-30 22:35 ` Vladimir Oltean
2020-11-30 22:50 ` Rasmus Villemoes
2020-11-30 23:11 ` Andrew Lunn
2020-12-05 14:49 ` vlan_filtering=1 breaks all traffic (was: Re: warnings from MTU setting on switch ports) Rasmus Villemoes
2020-12-05 15:45 ` Russell King - ARM Linux admin
2020-12-05 16:02 ` vlan_filtering=1 breaks all traffic Rasmus Villemoes
2020-12-05 19:03 ` vlan_filtering=1 breaks all traffic (was: Re: warnings from MTU setting on switch ports) Vladimir Oltean
2020-12-05 20:13 ` vlan_filtering=1 breaks all traffic Rasmus Villemoes
2020-12-06 19:45 ` Vladimir Oltean
2020-12-07 19:43 ` Rasmus Villemoes
2020-12-07 20:15 ` Vladimir Oltean
2020-12-08 2:22 ` Andrew Lunn [this message]
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=20201208022223.GF2475764@lunn.ch \
--to=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=rasmus.villemoes@prevas.dk \
--cc=vladimir.oltean@nxp.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.