From: Ben Hutchings <bhutchings@solarflare.com>
To: Shmulik Ravid <shmulikr@broadcom.com>
Cc: davem@davemloft.net, John Fastabend <john.r.fastabend@intel.com>,
Eilon Greenstein <eilong@broadcom.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6 1/2] dcbnl: add support for retrieving peer configuration - ieee
Date: Thu, 24 Feb 2011 19:42:39 +0000 [thread overview]
Message-ID: <1298576559.2613.40.camel@bwh-desktop> (raw)
In-Reply-To: <1298581410.8877.21.camel@lb-tlvb-shmulik.il.broadcom.com>
On Thu, 2011-02-24 at 23:03 +0200, Shmulik Ravid wrote:
> These 2 patches add the support for retrieving the remote or peer DCBX
> configuration via dcbnl for embedded DCBX stacks. The peer configuration
> is part of the DCBX MIB and is useful for debugging and diagnostics of
> the overall DCB configuration. The first patch add this support for IEEE
> 802.1Qaz standard the second patch add the same support for the older
> CEE standard.
>
> Signed-off-by: Shmulik Ravid <shmulikr@broadcom.com>
> ---
> include/linux/dcbnl.h | 38 ++++++++++++++++++++++++++
> include/net/dcbnl.h | 5 +++
> net/dcb/dcbnl.c | 71 +++++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 114 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/dcbnl.h b/include/linux/dcbnl.h
> index 4c5b26e..3102185 100644
> --- a/include/linux/dcbnl.h
> +++ b/include/linux/dcbnl.h
> @@ -110,6 +110,22 @@ struct dcb_app {
> __u16 protocol;
> };
>
> +/* This structure contains the APP feature information sent by the peer.
> + * It is used for both the IEEE 802.1Qaz and the CEE flavors.
> + *
> + * @willing: willing bit in the peer APP tlv
> + * @error: error bit in the peer APP tlv
> + * @app_count: The number of objects in the peer APP table.
[...]
It looks like this was supposed to be a kernel-doc comment, but it's not
valid as such unless you start with:
/**
* struct dcb_peer_app_info - one-line description here
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-02-24 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 21:03 [PATCH net-next-2.6 1/2] dcbnl: add support for retrieving peer configuration - ieee Shmulik Ravid
2011-02-24 19:42 ` Ben Hutchings [this message]
2011-02-24 22:04 ` Shmulik Ravid - Rabinovitz
2011-02-24 20:37 ` John Fastabend
2011-02-24 22:03 ` Shmulik Ravid - Rabinovitz
2011-02-25 4:58 ` John Fastabend
2011-02-25 9:58 ` Shmulik Ravid - Rabinovitz
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=1298576559.2613.40.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eilong@broadcom.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shmulikr@broadcom.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).