From: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
To: dev@dpdk.org
Cc: jingjing.wu@intel.com, pablo.de.lara.guarch@intel.com
Subject: [dpdk-dev] [PATCH 0/2] fixes for icc build errors
Date: Mon, 4 Apr 2016 10:46:49 +0200 [thread overview]
Message-ID: <1459759611-13788-1-git-send-email-danielx.t.mrzyglod@intel.com> (raw)
This series of patches is to solve errors for Intel C Compiler
Daniel Mrzyglod (2):
examples/l2fwd-crypto: fix for icc
examples: fix build errors for icc
examples/ipsec-secgw/Makefile | 4 ++++
examples/l2fwd-crypto/main.c | 4 ++--
examples/vmdq_dcb/Makefile | 4 +++-
3 files changed, 9 insertions(+), 3 deletions(-)
--
2.5.5
next reply other threads:[~2016-04-04 8:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 8:46 Daniel Mrzyglod [this message]
2016-04-04 8:46 ` [dpdk-dev] [PATCH 1/2] examples/l2fwd-crypto: fix for icc Daniel Mrzyglod
2016-04-04 9:34 ` De Lara Guarch, Pablo
2016-04-04 8:46 ` [dpdk-dev] [PATCH 2/2] examples: fix build errors " Daniel Mrzyglod
2016-04-04 9:33 ` De Lara Guarch, Pablo
2016-04-04 9:38 ` Mrzyglod, DanielX T
2016-04-04 10:26 ` De Lara Guarch, Pablo
2016-04-04 10:56 ` [dpdk-dev] [PATCH v2] " Daniel Mrzyglod
2016-04-04 13:07 ` [dpdk-dev] [PATCH 0/2] fixes for icc build errors Thomas Monjalon
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=1459759611-13788-1-git-send-email-danielx.t.mrzyglod@intel.com \
--to=danielx.t.mrzyglod@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=pablo.de.lara.guarch@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).