From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev <dev@dpdk.org>, dpdk stable <stable@dpdk.org>,
Fan Zhang <roy.fan.zhang@intel.com>,
Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-dev] [PATCH] crypto/scheduler: fix header install with meson
Date: Thu, 17 Sep 2020 17:33:23 +0200 [thread overview]
Message-ID: <CAJFAV8wcfujv7QPv4Bb4rG0SG3Zi44ZNiMotDbAYe8_gqSY8hw@mail.gmail.com> (raw)
In-Reply-To: <20200917152920.GH1568@bricha3-MOBL.ger.corp.intel.com>
On Thu, Sep 17, 2020 at 5:29 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> On Thu, Sep 17, 2020 at 05:09:17PM +0200, David Marchand wrote:
> > The headers variable is only used in lib/meson.build context.
> > For drivers, an explicit install_headers() is necessary.
> >
> > Reproduced while compiling the l2fwd-crypto example out of meson
> > (which can be done by adding it in devtools/test-meson-builds.sh
> > examples build test).
> >
> > Fixes: cd2b6458a1cb ("crypto/scheduler: add in meson build")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > ---
> > drivers/crypto/scheduler/meson.build | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> Originally I only put the "headers" variable in the "lib" folder
> meson.build because it was not expected that many drivers should have
> private headers. However, perhaps it's worthwhile adding it now:
> a) because private headers, while not common, are not unusual
> b) for consistency and ease of use.
>
> Thoughts?
Yep, I can do it in a followup patch now, still looking at your RFC
series though.. :-)
--
David Marchand
next prev parent reply other threads:[~2020-09-17 15:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 15:09 David Marchand
2020-09-17 15:29 ` Bruce Richardson
2020-09-17 15:33 ` David Marchand [this message]
2020-09-17 15:46 ` Bruce Richardson
2020-09-17 15:29 ` Bruce Richardson
2020-10-22 7:55 ` [dpdk-dev] [PATCH v2 1/2] " David Marchand
2020-10-22 7:55 ` [dpdk-dev] [PATCH v2 2/2] drivers: add headers install helper David Marchand
2020-10-22 8:16 ` Bruce Richardson
2020-10-22 8:22 ` David Marchand
2020-10-22 9:47 ` Luca Boccassi
2020-10-22 9:53 ` Kevin Traynor
2020-10-22 12:32 ` David Marchand
2020-10-23 7:22 ` Xu, Rosen
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=CAJFAV8wcfujv7QPv4Bb4rG0SG3Zi44ZNiMotDbAYe8_gqSY8hw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@intel.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).