From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH 2/5] compressdev: separate out driver-only headers
Date: Fri, 11 Mar 2022 20:05:20 +0000 [thread overview]
Message-ID: <20220311200523.1020050-3-bruce.richardson@intel.com> (raw)
In-Reply-To: <20220311200523.1020050-1-bruce.richardson@intel.com>
The headers rte_compressdev_pmd.h and rte_compressdev_internal.h are,
as the filenames suggest, headers for building drivers using the
compressdev APIs. As such they should be marked as
"driver_sdk_headers" rather than just "headers" in the meson.build
file.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
lib/compressdev/meson.build | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/lib/compressdev/meson.build b/lib/compressdev/meson.build
index 75ea666a9b..c80295dc0d 100644
--- a/lib/compressdev/meson.build
+++ b/lib/compressdev/meson.build
@@ -11,7 +11,9 @@ sources = files('rte_compressdev.c',
'rte_compressdev_pmd.c',
'rte_comp.c')
headers = files('rte_compressdev.h',
- 'rte_compressdev_pmd.h',
- 'rte_compressdev_internal.h',
'rte_comp.h')
+driver_sdk_headers = files(
+ 'rte_compressdev_pmd.h',
+ 'rte_compressdev_internal.h',
+ )
deps += ['kvargs', 'mbuf']
--
2.34.1
next prev parent 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 [PATCH 0/5] build fixes on FreeBSD Bruce Richardson
2022-03-11 20:05 ` [PATCH 1/5] eal/freebsd: add missing C++ include guards Bruce Richardson
2022-03-11 20:05 ` Bruce Richardson [this message]
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-3-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).