From: Kevin Traynor <ktraynor@redhat.com>
To: David Marchand <david.marchand@redhat.com>, stable@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-stable] [PATCH 18.11] crypto/scheduler: fix header install with meson
Date: Fri, 30 Oct 2020 13:09:43 +0000 [thread overview]
Message-ID: <60cfcbdb-c0ce-b034-df65-0ae4c4a04600@redhat.com> (raw)
In-Reply-To: <20201022123250.5168-1-david.marchand@redhat.com>
On 22/10/2020 13:32, 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")
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
Applied, thanks.
prev parent reply other threads:[~2020-10-30 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 12:32 David Marchand
2020-10-30 13:09 ` Kevin Traynor [this message]
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=60cfcbdb-c0ce-b034-df65-0ae4c4a04600@redhat.com \
--to=ktraynor@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.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).