From: John Fastabend <john.r.fastabend@intel.com>
To: Shmulik Ravid <shmulikr@broadcom.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
Eilon Greenstein <eilong@broadcom.com>,
"Liu, Lucy" <lucy.liu@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [net-next-2.6 PATCH v2 1/4] dcbnl: adding DCBX engine capability
Date: Thu, 30 Dec 2010 11:09:20 -0800 [thread overview]
Message-ID: <4D1CD8E0.80202@intel.com> (raw)
In-Reply-To: <4D1CD560.3000609@intel.com>
On 12/30/2010 10:54 AM, John Fastabend wrote:
> On 12/30/2010 8:26 AM, Shmulik Ravid wrote:
>> Adding an optional DCBX capability and a pair for get-set routines for
>> setting the device DCBX mode. The DCBX capability is a bit field of
>> supported attributes. The user is expected to set the DCBX mode with a
>> subset of the advertised attributes.
>>
>> This patch is dependent on the following patches:
>> [net-next-2.6 PATCH 1/3] dcbnl: add support for ieee8021Qaz attributes
>> [net-next-2.6 PATCH 2/3] dcbnl: add appliction tlv handlers
>> [net-next-2.6 PATCH 3/3] net_dcb: add application notifiers
>>
>> Signed-off-by: Shmulik Ravid <shmulikr@broadcom.com>
>> ---
>
> Acked-by: John Fastabend <john.r.fastabend@intel.com>
>
> Thanks for doing this Shmulik.
>
Sorry missed this on my first pass.
>
> +/* DCBX configuration */
> +static int dcbnl_getdcbx(struct net_device *netdev, struct nlattr **tb,
> + u32 pid, u32 seq, u16 flags)
> +{
> + int ret = -EINVAL;
> +
> + if (!netdev->dcbnl_ops->getdcbx)
> + return ret;
I think we should actually return -EOPNOTSUPP here.
> +
> + ret = dcbnl_reply(netdev->dcbnl_ops->getdcbx(netdev), RTM_GETDCB,
> + DCB_CMD_GDCBX, DCB_ATTR_DCBX, pid, seq, flags);
> +
> + return ret;
> +}
> +
prev parent reply other threads:[~2010-12-30 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 16:26 [net-next-2.6 PATCH v2 1/4] dcbnl: adding DCBX engine capability Shmulik Ravid
2010-12-30 18:54 ` John Fastabend
2010-12-30 19:09 ` John Fastabend [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=4D1CD8E0.80202@intel.com \
--to=john.r.fastabend@intel.com \
--cc=davem@davemloft.net \
--cc=eilong@broadcom.com \
--cc=lucy.liu@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).