From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 0/4] fix examples build
Date: Tue, 16 Feb 2016 07:46:06 +0100 [thread overview]
Message-ID: <1455605170-16137-1-git-send-email-thomas.monjalon@6wind.com> (raw)
I've sent some patchsets previously to fixes examples:
- "fix build for default machine"
- "fix compilation of examples for ARM"
Gather the non-rejected patches of these series here.
Thomas Monjalon (4):
examples/l3fwd: fix build without SSE4.1
examples/ip_pipeline: fix build for x86_64 without SSE4.2
examples/ethtool: fix build
examples: fix build dependencies
examples/Makefile | 12 ++++++++----
examples/ethtool/ethtool-app/main.c | 2 +-
examples/ip_pipeline/pipeline/hash_func.h | 2 +-
examples/l3fwd/main.c | 3 ++-
4 files changed, 12 insertions(+), 7 deletions(-)
--
2.7.0
next reply other threads:[~2016-02-16 6:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 6:46 Thomas Monjalon [this message]
2016-02-16 6:46 ` [dpdk-dev] [PATCH v2 1/4] examples/l3fwd: fix build without SSE4.1 Thomas Monjalon
2016-02-16 6:46 ` [dpdk-dev] [PATCH v2 2/4] examples/ip_pipeline: fix build for x86_64 without SSE4.2 Thomas Monjalon
2016-03-30 13:24 ` Dumitrescu, Cristian
2016-03-30 13:58 ` Thomas Monjalon
2016-03-30 13:57 ` Dumitrescu, Cristian
2016-03-30 14:06 ` Thomas Monjalon
2016-03-30 14:15 ` Dumitrescu, Cristian
2016-03-30 15:50 ` Thomas Monjalon
2016-03-30 16:31 ` Dumitrescu, Cristian
2016-03-30 18:06 ` [dpdk-dev] [PATCH] examples/ip_pipeline: fix SSE4.2 optimization branch Thomas Monjalon
2016-03-31 20:49 ` Thomas Monjalon
2016-02-16 6:46 ` [dpdk-dev] [PATCH v2 3/4] examples/ethtool: fix build Thomas Monjalon
2016-02-16 6:46 ` [dpdk-dev] [PATCH v2 4/4] examples: fix build dependencies Thomas Monjalon
2016-02-16 6:56 ` [dpdk-dev] [PATCH v2 0/4] fix examples build 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=1455605170-16137-1-git-send-email-thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.com \
--cc=dev@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).