From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/2] enable pmdinfo support on FreeBSD
Date: Sat, 09 Jul 2016 23:57:38 +0200 [thread overview]
Message-ID: <28794679.xMvagz4XnB@xps13> (raw)
In-Reply-To: <1468010225-7260-1-git-send-email-bruce.richardson@intel.com>
2016-07-08 21:37, Bruce Richardson:
> This patchset fixes pmdinfogen and pmdinfo.py so that they can work on
> FreeBSD. It's been tested with static binaries compiled using clang and gcc
> on FreeBSD, as well as gcc-generated dynamic libraries. For some reason
> clang wasn't able to build dynamic libraries for DPDK on FreeBSD so that is
> untested. [Investigation of that issue is for another time]
>
> Bruce Richardson (2):
> pmdinfogen: fix build on FreeBSD
> scripts: fix pmdinfo for FreeBSD
Applied, thanks
prev parent reply other threads:[~2016-07-09 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 20:37 Bruce Richardson
2016-07-08 20:37 ` [dpdk-dev] [PATCH 1/2] pmdinfogen: fix build " Bruce Richardson
2016-07-08 20:37 ` [dpdk-dev] [PATCH 2/2] scripts: fix pmdinfo for FreeBSD Bruce Richardson
2016-07-09 21:57 ` 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=28794679.xMvagz4XnB@xps13 \
--to=thomas.monjalon@6wind.com \
--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).