DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kavanagh, Mark B" <mark.b.kavanagh@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: fix compilation
Date: Tue, 10 Oct 2017 07:40:52 +0000	[thread overview]
Message-ID: <DC5AD7FA266D86499789B1BCAEC715F8D3A248EC@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <6fec0ca0-4adc-9f35-0e2b-ec6d7a17b1d9@intel.com>

>From: Yigit, Ferruh
>Sent: Monday, October 9, 2017 6:34 PM
>To: Kavanagh, Mark B <mark.b.kavanagh@intel.com>; dev@dpdk.org
>Cc: ajit.khaparde@broadcom.com
>Subject: Re: [PATCH] net/bnxt: fix compilation
>
>On 10/9/2017 2:59 PM, Mark Kavanagh wrote:
>> As of 5ef3b79fdfe6f, compilation of DPDK fails with the following
>> error message:
>> "bnxt_filter.c:960:117: error: ‘vnic’ may be used uninitialized in this
>> function [-Werror=maybe-uninitialized]".
>>
>> Resolve this by initializing 'vnic' to NULL;
>>
>> Fixes: 5ef3b79fdfe6f ("net/bnxt: support flow filter ops")
>
>>
>> Signed-off-by: Mark Kavanagh <mark.b.kavanagh@intel.com>
>
>Applied to dpdk-next-net/master, thanks.
>
>Can you please provide compiler and version information?
>I get the commit for now and will update it later with that information.

Thanks Ferruh - compiler info is as follows:

   gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7)

Best,
Mark

  reply	other threads:[~2017-10-10  7:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 13:59 Mark Kavanagh
2017-10-09 14:14 ` [dpdk-dev] [dpdk-stable] " De Lara Guarch, Pablo
2017-10-09 14:28   ` Kavanagh, Mark B
2017-10-09 17:34 ` [dpdk-dev] " Ferruh Yigit
2017-10-10  7:40   ` Kavanagh, Mark B [this message]
2017-10-10 16:45     ` Ferruh Yigit

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=DC5AD7FA266D86499789B1BCAEC715F8D3A248EC@IRSMSX101.ger.corp.intel.com \
    --to=mark.b.kavanagh@intel.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).