From: David Marchand <david.marchand@redhat.com>
To: Haiyue Wang <haiyue.wang@intel.com>
Cc: dev <dev@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v17 1/2] eal: add uuid dependent header files explicitly
Date: Mon, 6 Jul 2020 16:32:11 +0200 [thread overview]
Message-ID: <CAJFAV8yoXBYq5CruRbR1ACDyV9xinp4L91eTHs13fv1SW0sfdQ@mail.gmail.com> (raw)
In-Reply-To: <20200703145718.81017-2-haiyue.wang@intel.com>
On Fri, Jul 3, 2020 at 5:05 PM Haiyue Wang <haiyue.wang@intel.com> wrote:
>
> Add the dependent header files explicitly, so that the user just needs
> to include the 'rte_uuid.h' header file directly to avoid compile error:
> (1). rte_uuid.h:97:55: error: unknown type name ‘size_t’
> (2). rte_uuid.h:58:2: error: implicit declaration of function ‘memcpy’
>
> Fixes: 6bc67c497a51 ("eal: add uuid API")
> Cc: stable@dpdk.org
>
> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
> ---
> lib/librte_eal/include/rte_uuid.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/lib/librte_eal/include/rte_uuid.h b/lib/librte_eal/include/rte_uuid.h
> index 044afbdfa..8b42e070a 100644
> --- a/lib/librte_eal/include/rte_uuid.h
> +++ b/lib/librte_eal/include/rte_uuid.h
> @@ -15,6 +15,8 @@ extern "C" {
> #endif
>
> #include <stdbool.h>
> +#include <stddef.h>
> +#include <string.h>
>
> /**
> * Struct describing a Universal Unique Identifier
> --
> 2.27.0
>
Acked-by: David Marchand <david.marchand@redhat.com>
--
David Marchand
prev parent reply other threads:[~2020-07-06 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200305043311.17065-1-vattunuru@marvell.com>
[not found] ` <20200414030625.35195-1-haiyue.wang@intel.com>
2020-04-14 3:06 ` [dpdk-stable] [PATCH v5 " Haiyue Wang
[not found] ` <20200418111642.78874-1-haiyue.wang@intel.com>
2020-04-18 11:16 ` [dpdk-stable] [PATCH v7 " Haiyue Wang
[not found] ` <20200418173035.8000-1-haiyue.wang@intel.com>
2020-04-18 17:30 ` [dpdk-stable] [PATCH v8 " Haiyue Wang
[not found] ` <20200422050804.66781-1-haiyue.wang@intel.com>
2020-04-22 5:08 ` [dpdk-stable] [PATCH v9 " Haiyue Wang
[not found] ` <20200426015514.39489-1-haiyue.wang@intel.com>
2020-04-26 1:55 ` [dpdk-stable] [PATCH v10 " Haiyue Wang
[not found] ` <20200505074646.31985-1-haiyue.wang@intel.com>
2020-05-05 7:46 ` [dpdk-stable] [PATCH v11 " Haiyue Wang
[not found] ` <20200505103440.38455-1-haiyue.wang@intel.com>
2020-05-05 10:34 ` [dpdk-stable] [PATCH v12 " Haiyue Wang
[not found] ` <20200506113524.30205-1-haiyue.wang@intel.com>
2020-05-06 11:35 ` [dpdk-stable] [PATCH v13 " Haiyue Wang
[not found] ` <20200528012225.74142-1-haiyue.wang@intel.com>
2020-05-28 1:22 ` [dpdk-stable] [PATCH v14 " Haiyue Wang
[not found] ` <20200529013710.72302-1-haiyue.wang@intel.com>
2020-05-29 1:37 ` [dpdk-stable] [PATCH v15 " Haiyue Wang
[not found] ` <20200617063321.52709-1-haiyue.wang@intel.com>
2020-06-17 6:33 ` [dpdk-stable] [PATCH v16 " Haiyue Wang
[not found] ` <20200703145718.81017-1-haiyue.wang@intel.com>
2020-07-03 14:57 ` [dpdk-stable] [PATCH v17 " Haiyue Wang
2020-07-06 14:32 ` David Marchand [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=CAJFAV8yoXBYq5CruRbR1ACDyV9xinp4L91eTHs13fv1SW0sfdQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=jerinj@marvell.com \
--cc=stable@dpdk.org \
--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).