From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Xie, Huawei" <huawei.xie@intel.com>
Cc: dev@dpdk.org, Hayato Momma <h-momma@ce.jp.nec.com>
Subject: Re: [dpdk-dev] [PATCH] rte_memory.h: include stdio.h for FILE
Date: Wed, 25 Jun 2014 11:51:24 +0200 [thread overview]
Message-ID: <1519995.xBIJsFhZji@xps13> (raw)
In-Reply-To: <C37D651A908B024F974696C65296B57B0F210465@SHSMSX101.ccr.corp.intel.com>
Hi Huawei,
2014-06-17 03:48, Xie, Huawei:
> At least rte_tailq.h, rte_mbuf.h should also include stdio.h.
It has been fixed in this commit:
http://dpdk.org/browse/dpdk/commit/?id=86d5de5c46fc0
But rte_memory.h was forgotten.
rte_mbuf.h has no problem because it includes rte_mempool.h which includes
stdio.h.
--
Thomas
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Hiroshi Shimamoto
> Sent: Thursday, June 12, 2014 4:11 PM
> To: dev@dpdk.org
> Cc: Hayato Momma
> Subject: [dpdk-dev] [PATCH] rte_memory.h: include stdio.h for FILE
>
> From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
>
> The below commit requires stdio FILE structure.
>
> commit 591a9d7985c1230652d9f7ea1f9221e8c66ec188
> Author: Stephen Hemminger <stephen@networkplumber.org>
> Date: Fri May 2 16:42:56 2014 -0700
>
> add FILE argument to debug functions
>
> Application which includes rte_memory.h without stdio.h will be hit
> compilation failure.
>
> /path/to/include/rte_memory.h:146:30: error: unknown type name 'FILE'
> void rte_dump_physmem_layout(FILE *f);
>
> Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
> Reviewed-by: Hayato Momma <h-momma@ce.jp.nec.com>
> ---
> lib/librte_eal/common/include/rte_memory.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/lib/librte_eal/common/include/rte_memory.h
> b/lib/librte_eal/common/include/rte_memory.h index 7f21244..4cf8ea9 100644
> --- a/lib/librte_eal/common/include/rte_memory.h
> +++ b/lib/librte_eal/common/include/rte_memory.h
> @@ -42,6 +42,7 @@
>
> #include <stdint.h>
> #include <stddef.h>
> +#include <stdio.h>
>
> #ifdef RTE_EXEC_ENV_LINUXAPP
> #include <exec-env/rte_dom0_common.h>
> --
> 1.9.1
next prev parent reply other threads:[~2014-06-25 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 8:10 Hiroshi Shimamoto
2014-06-17 3:48 ` Xie, Huawei
2014-06-25 9:51 ` Thomas Monjalon [this message]
2014-06-27 0:11 ` Thomas Monjalon
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=1519995.xBIJsFhZji@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=h-momma@ce.jp.nec.com \
--cc=huawei.xie@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).