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 4/4] dcbnl: cleanup
Date: Thu, 30 Dec 2010 11:17:41 -0800 [thread overview]
Message-ID: <4D1CDAD5.4010602@intel.com> (raw)
In-Reply-To: <1293726430.29378.95.camel@lb-tlvb-shmulik.il.broadcom.com>
On 12/30/2010 8:27 AM, Shmulik Ravid wrote:
> A couple of small cleanups for 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>
> ---
Good catch, thanks a lot. I will roll this into my patch and push a v2 so that we don't introduce a known bug. Of course I'll give you credit.
Thanks,
John.
> net/dcb/dcbnl.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/net/dcb/dcbnl.c b/net/dcb/dcbnl.c
> index b387816..ff3c12d 100644
> --- a/net/dcb/dcbnl.c
> +++ b/net/dcb/dcbnl.c
> @@ -1626,8 +1626,10 @@ u8 dcb_setapp(struct net_device *dev, struct dcb_app *new)
> if (new->priority) {
> struct dcb_app_type *entry;
> entry = kmalloc(sizeof(struct dcb_app_type), GFP_ATOMIC);
> - if (!entry)
> + if (!entry) {
> + spin_unlock(&dcb_lock);
> return -ENOMEM;
> + }
>
> memcpy(&entry->app, new, sizeof(*new));
> strncpy(entry->name, dev->name, IFNAMSIZ);
> @@ -1640,7 +1642,7 @@ out:
> }
> EXPORT_SYMBOL(dcb_setapp);
>
> -void dcb_flushapp(void)
> +static void dcb_flushapp(void)
> {
> struct dcb_app_type *app;
>
prev parent reply other threads:[~2010-12-30 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 16:27 [net-next-2.6 PATCH v2 4/4] dcbnl: cleanup Shmulik Ravid
2010-12-30 19:17 ` 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=4D1CDAD5.4010602@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).