From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/3] small fixes for FreeBSD builds
Date: Tue, 26 Feb 2019 16:29:16 +0100 [thread overview]
Message-ID: <2129010.bn8gvtJg9l@xps> (raw)
In-Reply-To: <20190225152304.62607-1-bruce.richardson@intel.com>
25/02/2019 16:23, Bruce Richardson:
> Set of three one-line fixes to improve the FreeBSD builds, particularly with
> -Dexamples=all set for meson builds.
>
> Bruce Richardson (3):
> test/compress: fix missing header include
> examples/ip_pipeline: disable build when no epoll
> examples/vhost_crypto: fix dependency on vhost library
Applied, thanks
prev parent reply other threads:[~2019-02-26 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 15:23 Bruce Richardson
2019-02-25 15:23 ` [dpdk-dev] [PATCH 1/3] test/compress: fix missing header include Bruce Richardson
2019-02-25 15:23 ` [dpdk-dev] [PATCH 2/3] examples/ip_pipeline: disable build when no epoll Bruce Richardson
2019-02-25 15:23 ` [dpdk-dev] [PATCH 3/3] examples/vhost_crypto: fix dependency on vhost library Bruce Richardson
2019-02-25 16:24 ` Maxime Coquelin
2019-02-26 15:29 ` 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=2129010.bn8gvtJg9l@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 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).