From: Ray Kinsella <mdr@ashroe.eu>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
dev@dpdk.org, david.marchand@redhat.com
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v8 08/13] mempool/dpaa2: fix to add the include file
Date: Tue, 19 May 2020 12:18:48 +0100 [thread overview]
Message-ID: <4ea54d04-1269-3a95-a740-cdc501636357@ashroe.eu> (raw)
In-Reply-To: <20200515094752.28490-9-hemant.agrawal@nxp.com>
On 15/05/2020 10:47, Hemant Agrawal wrote:
> rte_dpaa2_mempool.h header was missed to be
> added in meson.build for header installation.
>
> Fixes: 7ed359909556 ("mempool/dpaa2: add functions for CMDIF")
> Cc: stable@dpdk.org
>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
> drivers/mempool/dpaa2/meson.build | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/mempool/dpaa2/meson.build b/drivers/mempool/dpaa2/meson.build
> index df299a0456..c3f479afa1 100644
> --- a/drivers/mempool/dpaa2/meson.build
> +++ b/drivers/mempool/dpaa2/meson.build
> @@ -8,3 +8,5 @@ endif
>
> deps += ['bus_fslmc']
> sources = files('dpaa2_hw_mempool.c')
> +
> +install_headers('rte_dpaa2_mempool.h')
>
Acked-by: Ray Kinsella <mdr@ashroe.eu>
prev parent reply other threads:[~2020-05-19 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200513132745.9006-1-hemant.agrawal@nxp.com>
[not found] ` <20200514132533.13752-1-hemant.agrawal@nxp.com>
2020-05-14 13:25 ` [dpdk-stable] [PATCH v4 " Hemant Agrawal
[not found] ` <20200514142951.31801-1-hemant.agrawal@nxp.com>
2020-05-14 14:29 ` [dpdk-stable] [PATCH v6 " Hemant Agrawal
[not found] ` <20200515050831.22834-1-hemant.agrawal@nxp.com>
2020-05-15 5:08 ` [dpdk-stable] [PATCH v7 " Hemant Agrawal
[not found] ` <20200515094752.28490-1-hemant.agrawal@nxp.com>
2020-05-15 9:47 ` [dpdk-stable] [PATCH v8 " Hemant Agrawal
2020-05-19 11:18 ` Ray Kinsella [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=4ea54d04-1269-3a95-a740-cdc501636357@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.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).