From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Kavanagh, Mark B" <mark.b.kavanagh@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
"Kavanagh, Mark B" <mark.b.kavanagh@intel.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/bnxt: fix compilation
Date: Mon, 9 Oct 2017 14:14:36 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC2E2D9@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1507557570-11483-1-git-send-email-mark.b.kavanagh@intel.com>
> -----Original Message-----
> From: stable [mailto:stable-bounces@dpdk.org] On Behalf Of Mark
> Kavanagh
> Sent: Monday, October 9, 2017 3:00 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>;
> ajit.khaparde@broadcom.com; Kavanagh, Mark B
> <mark.b.kavanagh@intel.com>
> Subject: [dpdk-stable] [PATCH] net/bnxt: fix compilation
>
> 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")
> CC: stable@dpdk.org
Hi Mark,
You don't need to cc stable, since you are fixing code that was sent in this release.
Only fixes for patches sent in previous DPDK versions need to be applied to the stable repo.
Regards,
Pablo
next prev parent reply other threads:[~2017-10-09 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 13:59 [dpdk-dev] " Mark Kavanagh
2017-10-09 14:14 ` De Lara Guarch, Pablo [this message]
2017-10-09 14:28 ` [dpdk-dev] [dpdk-stable] " Kavanagh, Mark B
2017-10-09 17:34 ` [dpdk-dev] " Ferruh Yigit
2017-10-10 7:40 ` Kavanagh, Mark B
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=E115CCD9D858EF4F90C690B0DCB4D8976CC2E2D9@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=mark.b.kavanagh@intel.com \
--cc=stable@dpdk.org \
/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).