From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org, ssujith@cisco.com
Subject: [dpdk-dev] [PATCH 0/2] enic fixes for clang compilation
Date: Fri, 5 Dec 2014 15:57:10 +0000 [thread overview]
Message-ID: <1417795032-23524-1-git-send-email-bruce.richardson@intel.com> (raw)
Compiling latest DPDK with clang 3.3 on FreeBSD 10 shows up a number of compilation
errors in the enic driver. These two small patches fix those errors.
Bruce Richardson (2):
enic: fix initialization error with clang
enic: fix error with uninitialized variable.
lib/librte_pmd_enic/enic_clsf.c | 2 +-
lib/librte_pmd_enic/vnic/vnic_dev.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.1.0
next reply other threads:[~2014-12-05 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 15:57 Bruce Richardson [this message]
2014-12-05 15:57 ` [dpdk-dev] [PATCH 1/2] enic: fix initialization error with clang Bruce Richardson
2014-12-05 15:57 ` [dpdk-dev] [PATCH 2/2] enic: fix error with uninitialized variable Bruce Richardson
2014-12-05 21:11 ` [dpdk-dev] [PATCH 0/2] enic fixes for clang compilation Thomas Monjalon
2014-12-07 15:21 ` Sujith Sankar (ssujith)
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=1417795032-23524-1-git-send-email-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ssujith@cisco.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).