From: Or Gerlitz <gerlitz.or@gmail.com>
To: Hariprasad Shenai <hariprasad@chelsio.com>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
leedom@chelsio.com, nirranjan@chelsio.com,
John Fastabend <john.r.fastabend@intel.com>
Subject: Re: [PATCH net-next 3/5] cxgb4: add dcb info node in debugfs
Date: Mon, 21 Dec 2015 09:33:22 +0200 [thread overview]
Message-ID: <CAJ3xEMjctGauyRjCKLV+wACkzDC5xF8J9khdhCm+YZXuEafU5Q@mail.gmail.com> (raw)
In-Reply-To: <1450682170-7106-4-git-send-email-hariprasad@chelsio.com>
On Mon, Dec 21, 2015 at 9:16 AM, Hariprasad Shenai
<hariprasad@chelsio.com> wrote:
> Add new /sys/kernel/debug/cxgb4/*/dcb_info node to dump out
> various Data Center Bridging information.
why? what's wrong with using the lldp tool for that purpose?
next prev parent reply other threads:[~2015-12-21 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 7:16 [PATCH net-next 0/5] Trivial enhancements for cxgb4 Hariprasad Shenai
2015-12-21 7:16 ` [PATCH net-next 1/5] cxgb4: Warn if device doesn't have enough PCI bandwidth Hariprasad Shenai
2015-12-21 7:16 ` [PATCH net-next 2/5] cxgb4: get naming correct for iscsi queues Hariprasad Shenai
2015-12-21 7:16 ` [PATCH net-next 3/5] cxgb4: add dcb info node in debugfs Hariprasad Shenai
2015-12-21 7:33 ` Or Gerlitz [this message]
2015-12-22 11:41 ` Hariprasad S
2015-12-22 20:45 ` David Miller
2015-12-23 5:07 ` Hariprasad Shenai
2015-12-21 7:16 ` [PATCH net-next 4/5] cxgb4: Use the node info to alloc_ring() for RX queues Hariprasad Shenai
2015-12-21 7:16 ` [PATCH net-next 5/5] cxgb4: Use napi_complete_done() api in napi handler Hariprasad Shenai
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=CAJ3xEMjctGauyRjCKLV+wACkzDC5xF8J9khdhCm+YZXuEafU5Q@mail.gmail.com \
--to=gerlitz.or@gmail.com \
--cc=davem@davemloft.net \
--cc=hariprasad@chelsio.com \
--cc=john.r.fastabend@intel.com \
--cc=leedom@chelsio.com \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.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).