patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Haiyue Wang <haiyue.wang@intel.com>
To: dev@dpdk.org, anatoly.burakov@intel.com, thomas@monjalon.net,
	jerinj@marvell.com, david.marchand@redhat.com,
	arybchenko@solarflare.com, xiaolong.ye@intel.com
Cc: Haiyue Wang <haiyue.wang@intel.com>, stable@dpdk.org
Subject: [dpdk-stable] [PATCH v16 1/2] eal: add uuid dependent header files explicitly
Date: Wed, 17 Jun 2020 14:33:20 +0800	[thread overview]
Message-ID: <20200617063321.52709-2-haiyue.wang@intel.com> (raw)
In-Reply-To: <20200617063321.52709-1-haiyue.wang@intel.com>

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


  parent reply	other threads:[~2020-06-17  6:42 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   ` Haiyue Wang [this message]
     [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

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=20200617063321.52709-2-haiyue.wang@intel.com \
    --to=haiyue.wang@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=arybchenko@solarflare.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=xiaolong.ye@intel.com \
    /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).