From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 0/4] Fixes for BSD compilation
Date: Fri, 21 Apr 2017 16:12:55 +0200 [thread overview]
Message-ID: <2956624.lMtmS5PMlv@xps> (raw)
In-Reply-To: <20170421135024.25323-1-bruce.richardson@intel.com>
21/04/2017 15:50, Bruce Richardson:
> Fixes a number of issues with compiling on BSD, and a general fix to
> clean up the compilation of the performance-thread app.
>
> V2 changes:
> * adjust fix for perf thread compilation to use rte_lcore.h
> instead of extra #ifdefs.
> * added in two extra patches, enabling examples_clean to run
> on BSD, and removing the "common" build dir in perf thread example.
>
>
> Bruce Richardson (4):
> net/ark: fix FreeBSD compilation
> examples: fix examples_clean build target on FreeBSD
> examples/performance-thread: fix FreeBSD compilation
> examples/performance-thread: use a single build output dir
Applied, thanks
prev parent reply other threads:[~2017-04-21 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 16:32 [PATCH 0/2] fixes for FreeBSD compilation Bruce Richardson
2017-04-20 16:32 ` [PATCH 1/2] examples/performance-thread: fix " Bruce Richardson
2017-04-20 17:33 ` [dpdk-stable] " Thomas Monjalon
2017-04-20 16:32 ` [PATCH 2/2] net/ark: " Bruce Richardson
2017-04-20 17:23 ` john miller
2017-04-21 13:50 ` [PATCH v2 0/4] Fixes for BSD compilation Bruce Richardson
2017-04-21 13:50 ` [PATCH v2 1/4] net/ark: fix FreeBSD compilation Bruce Richardson
2017-04-21 13:50 ` [PATCH v2 2/4] examples: fix examples_clean build target on FreeBSD Bruce Richardson
2017-04-21 13:50 ` [PATCH v2 3/4] examples/performance-thread: fix FreeBSD compilation Bruce Richardson
2017-04-21 13:50 ` [PATCH v2 4/4] examples/performance-thread: use a single build output dir Bruce Richardson
2017-04-21 14:12 ` Thomas Monjalon [this message]
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=2956624.lMtmS5PMlv@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.