From: Brian Dooley <brian.dooley@intel.com>
To: stable@dpdk.org
Cc: christian.ehrhardt@canonical.com, Brian Dooley <brian.dooley@intel.com>
Subject: [PATCH 19.11 0/3] add missing C++ guards
Date: Tue, 15 Mar 2022 09:46:05 +0000 [thread overview]
Message-ID: <20220315094608.1199076-1-brian.dooley@intel.com> (raw)
Public header files were missing 'extern "C"' guards.
This set adds them in.
Brian Dooley (3):
eal: fix missing C++ guards
ethdev: add missing C++ guards
vhost: add missing c++ guards
lib/librte_eal/common/include/rte_branch_prediction.h | 8 ++++++++
lib/librte_eal/common/include/rte_compat.h | 8 ++++++++
lib/librte_eal/common/include/rte_hypervisor.h | 8 ++++++++
lib/librte_eal/common/include/rte_keepalive.h | 8 ++++++++
lib/librte_eal/common/include/rte_pci_dev_feature_defs.h | 8 ++++++++
lib/librte_eal/common/include/rte_pci_dev_features.h | 8 ++++++++
lib/librte_eal/common/include/rte_time.h | 8 ++++++++
lib/librte_eal/linux/eal/include/rte_os.h | 8 ++++++++
lib/librte_ethdev/rte_dev_info.h | 8 ++++++++
lib/librte_ethdev/rte_ethdev_pci.h | 8 ++++++++
lib/librte_ethdev/rte_ethdev_vdev.h | 8 ++++++++
lib/librte_vhost/rte_vdpa.h | 9 +++++++++
lib/librte_vhost/rte_vhost_crypto.h | 8 ++++++++
13 files changed, 105 insertions(+)
--
2.25.1
next reply other threads:[~2022-03-15 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 9:46 Brian Dooley [this message]
2022-03-15 9:46 ` [PATCH 19.11 1/3] eal: fix " Brian Dooley
2022-03-15 9:46 ` [PATCH 19.11 2/3] ethdev: add " Brian Dooley
2022-03-15 9:46 ` [PATCH 19.11 3/3] vhost: add missing c++ guards Brian Dooley
2022-03-17 9:00 ` [PATCH 19.11 0/3] add missing C++ guards Christian Ehrhardt
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=20220315094608.1199076-1-brian.dooley@intel.com \
--to=brian.dooley@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=stable@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).