DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH 0/5] build fixes on FreeBSD
Date: Fri, 11 Mar 2022 20:05:18 +0000	[thread overview]
Message-ID: <20220311200523.1020050-1-bruce.richardson@intel.com> (raw)

This set contains a number of fixes, most of which are for
build issues discovered when compiling on FreeBSD with clang.

Bruce Richardson (5):
  eal/freebsd: add missing C++ include guards
  compressdev: separate out driver-only headers
  compressdev: fix missing space in header
  cryptodev: fix compilation with clang C++ builds
  eventdev:  fix compilation with clang C++ builds

 lib/compressdev/meson.build                |  6 ++++--
 lib/compressdev/rte_compressdev_internal.h |  2 +-
 lib/cryptodev/rte_crypto.h                 |  9 +++++++++
 lib/eal/freebsd/include/rte_os.h           |  8 ++++++++
 lib/eventdev/rte_eventdev.h                | 12 +++++++++++-
 5 files changed, 33 insertions(+), 4 deletions(-)

--
2.34.1


             reply	other threads:[~2022-03-11 20:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 20:05 Bruce Richardson [this message]
2022-03-11 20:05 ` [PATCH 1/5] eal/freebsd: add missing C++ include guards Bruce Richardson
2022-03-11 20:05 ` [PATCH 2/5] compressdev: separate out driver-only headers Bruce Richardson
2022-03-11 20:05 ` [PATCH 3/5] compressdev: fix missing space in header Bruce Richardson
2022-03-11 20:05 ` [PATCH 4/5] cryptodev: fix compilation with clang C++ builds Bruce Richardson
2022-03-11 20:05 ` [PATCH 5/5] eventdev: " Bruce Richardson
2022-03-12  1:11   ` Stephen Hemminger
2022-03-14  9:00     ` Bruce Richardson
2022-03-15  1:13 ` [PATCH 0/5] build fixes on FreeBSD 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=20220311200523.1020050-1-bruce.richardson@intel.com \
    --to=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).