From: Bruce Richardson <bruce.richardson@intel.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: dev@dpdk.org, thomas@monjalon.net, ferruh.yigit@intel.com,
andrew.rybchenko@oktetlabs.ru
Subject: Re: [dpdk-dev] [PATCH v2] ethdev: introduce enable_driver_sdk to install driver headers
Date: Mon, 15 Mar 2021 10:06:25 +0000 [thread overview]
Message-ID: <20210315100625.GB2040@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <1615587606-29329-1-git-send-email-roretzla@linux.microsoft.com>
On Fri, Mar 12, 2021 at 02:20:06PM -0800, Tyler Retzlaff wrote:
> Introduce a meson option enable_driver_sdk when true installs internal
> driver headers for ethdev. this allows drivers that do not depend on
> stable api/abi to be built external to the dpdk source tree.
>
> Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
> ---
> lib/librte_ethdev/meson.build | 6 ++++++
> lib/meson.build | 4 ++++
> meson_options.txt | 2 ++
> 3 files changed, 12 insertions(+)
>
The infrastructure looks good to me. However, you need to add change to the
cryptodev, eventdev, etc. to add the headers from there too.
next prev parent reply other threads:[~2021-03-15 10:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 19:27 [dpdk-dev] [PATCH] " Tyler Retzlaff
2021-03-12 15:19 ` Ferruh Yigit
2021-03-12 15:25 ` David Marchand
2021-03-12 15:34 ` Bruce Richardson
2021-03-12 15:52 ` Thomas Monjalon
2021-03-12 18:43 ` Tyler Retzlaff
2021-03-12 22:20 ` [dpdk-dev] [PATCH v2] " Tyler Retzlaff
2021-03-15 10:06 ` Bruce Richardson [this message]
2021-03-23 17:04 ` Ferruh Yigit
2021-03-24 4:32 ` Tyler Retzlaff
2021-03-24 11:27 ` Ferruh Yigit
2021-03-24 11:30 ` Thomas Monjalon
2021-03-24 16:24 ` Tyler Retzlaff
2021-03-26 12:02 ` Ferruh Yigit
2021-03-26 20:52 ` Tyler Retzlaff
2021-03-29 9:43 ` Ferruh Yigit
2021-03-29 12:10 ` Thomas Monjalon
2021-03-29 15:23 ` Ferruh Yigit
2021-03-29 19:31 ` Thomas Monjalon
2021-03-30 12:50 ` Ferruh Yigit
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=20210315100625.GB2040@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=roretzla@linux.microsoft.com \
--cc=thomas@monjalon.net \
/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).