From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: salil.mehta@huawei.com, yisen.zhuang@huawei.com,
lipeng321@huawei.com, mehta.salil@opnsrc.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, liuzhongzhu@huawei.com, jiri@resnulli.us,
f.fainelli@gmail.com
Subject: Re: [RFC net-next 3/9] net: hns3: Add "port vlan table" information query function
Date: Mon, 03 Dec 2018 15:12:53 -0800 (PST) [thread overview]
Message-ID: <20181203.151253.1348214769326219632.davem@davemloft.net> (raw)
In-Reply-To: <20181203151222.6e56efcd@cakuba.netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Mon, 3 Dec 2018 15:12:22 -0800
> On Sun, 2 Dec 2018 23:09:27 +0000, Salil Mehta wrote:
>> From: liuzhongzhu <liuzhongzhu@huawei.com>
>>
>> This patch prints port vlan table information.
>>
>> debugfs command:
>> echo dump port vlan tbl > cmd
>>
>> Sample Command:
>> root@(none)# echo dump port vlan tbl > cmd
>> vlan | port filter bitMap:
>> 0000 | 00000000:00000000:00000000:00000000:00000000:00000001
>> root@(none)#
>>
>> Signed-off-by: liuzhongzhu <liuzhongzhu@huawei.com>
>> Signed-off-by: Salil Mehta <salil.mehta@huawei.com>
>
> Adding debugfs files for basic switch concepts like MAC and VLAN tables
> seems like a bit of a stretch to me. I wonder what others think.
Agreed.
next prev parent reply other threads:[~2018-12-03 23:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 23:09 [RFC net-next 0/9] net: hns3: Add more commands to Debugfs in HNS3 driver Salil Mehta
2018-12-02 23:09 ` [RFC net-next 1/9] net: hns3: Add "bd info" query function Salil Mehta
2018-12-02 23:09 ` [RFC net-next 2/9] net: hns3: Add "mac table" information " Salil Mehta
2018-12-02 23:09 ` [RFC net-next 3/9] net: hns3: Add "port vlan " Salil Mehta
2018-12-03 23:12 ` Jakub Kicinski
2018-12-03 23:12 ` David Miller [this message]
2018-12-04 10:10 ` Salil Mehta
2018-12-04 10:55 ` Andrew Lunn
2018-12-04 20:55 ` Salil Mehta
2018-12-02 23:09 ` [RFC net-next 4/9] net: hns3: Add "vf " Salil Mehta
2018-12-02 23:09 ` [RFC net-next 5/9] net: hns3: Add "manager " Salil Mehta
2018-12-02 23:09 ` [RFC net-next 6/9] net: hns3: Add "status register" " Salil Mehta
2018-12-02 23:09 ` [RFC net-next 7/9] net: hns3: Add "dcb register" status " Salil Mehta
2018-12-02 23:09 ` [RFC net-next 8/9] net: hns3: Add "queue map" " Salil Mehta
2018-12-02 23:09 ` [RFC net-next 9/9] net: hns3: Add "tm map" status " Salil Mehta
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=20181203.151253.1348214769326219632.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lipeng321@huawei.com \
--cc=liuzhongzhu@huawei.com \
--cc=mehta.salil@opnsrc.net \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=yisen.zhuang@huawei.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;
as well as URLs for NNTP newsgroup(s).