From: Andrew Lunn <andrew@lunn.ch>
To: Andrey Melnikov <temnota.am@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH net-next v3 5/5] net-next: dsa: add dsa support for Mediatek MT7530 switch
Date: Mon, 29 May 2017 17:29:26 +0200 [thread overview]
Message-ID: <20170529152926.GA21315@lunn.ch> (raw)
In-Reply-To: <CA+PODjoZpYLVKCXveUGvu8MXX4YVmE-bKm241o_3OT3P5pkieQ@mail.gmail.com>
> I want to see each ports behind the bridge as independent ethernet
> devices. If I understand RTFM only devlink may expose this
> configuration.
DSA and switchdev in general gives you a linux interface per user
switch port. So you can see each interface, get stats, ethtools,
mii-tool, etc per interface. devlink is not needed for this.
Andrew
prev parent reply other threads:[~2017-05-29 15:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 9:38 [PATCH net-next v3 0/5] net-next: dsa: add Mediatek MT7530 support sean.wang
2017-03-29 9:38 ` [PATCH net-next v3 1/5] dt-bindings: net: dsa: add Mediatek MT7530 binding sean.wang
2017-03-29 9:38 ` [PATCH net-next v3 2/5] net-next: dsa: add Mediatek tag RX/TX handler sean.wang
2017-03-29 9:38 ` [PATCH net-next v3 3/5] net-next: ethernet: mediatek: add CDM able to recognize the tag for DSA sean.wang
2017-03-29 9:38 ` [PATCH net-next v3 4/5] net-next: ethernet: mediatek: add device_node of GMAC pointing into the netdev instance sean.wang
2017-03-29 9:38 ` [PATCH net-next v3 5/5] net-next: dsa: add dsa support for Mediatek MT7530 switch sean.wang
2017-03-29 23:12 ` Andrew Lunn
2017-04-03 1:16 ` kbuild test robot
2017-04-03 5:06 ` kbuild test robot
2017-05-24 11:17 ` Andrey Jr. Melnikov
2017-05-24 13:20 ` Andrew Lunn
2017-05-24 14:44 ` Andrey Melnikov
2017-05-26 5:54 ` Florian Fainelli
2017-05-29 10:44 ` Andrey Melnikov
2017-05-29 15:29 ` 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=20170529152926.GA21315@lunn.ch \
--to=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=temnota.am@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
Powered by JetHome