DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "卢 毅" <luyi68@live.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: fix compile error in eal_timer.c caused by hpet
Date: Wed, 02 Mar 2016 17:45:06 +0100	[thread overview]
Message-ID: <5302405.qOPCxYW0H8@xps13> (raw)
In-Reply-To: <KL1PR0401MB1301A913A318D66496DC6299A4DA0@KL1PR0401MB1301.apcprd04.prod.outlook.com>

2016-01-28 14:16, 卢 毅:
> Fix compile error when enable CONFIG_RTE_LIBEAL_USE_HPET.
> 
> Error messages:
> /root/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_timer.c: In function ‘rte_eal_hpet_init’:
> /root/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_timer.c:222:2: error: implicit declaration of function ‘rte_thread_setname’ [-Werror=implicit-function-declaration]
>   ret = rte_thread_setname(msb_inc_thread_id, thread_name);
>   ^
> /root/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_timer.c:222:2: error: nested extern declaration of ‘rte_thread_setname’ [-Werror=nested-externs]
> cc1: all warnings being treated as errors
> 
> Fixes: badb3688ffa8 ("eal/linux: fix build with glibc < 2.12")

Just looking at the first letters of this SHA1 gives a hint ;)

> Signed-off-by: Yi Lu <luyi68@live.com>
> Acked-by: David Marchand <david.marchand@6wind.com>

Applied, thanks

      reply	other threads:[~2016-03-02 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-03 14:49 [dpdk-dev] [PATCH] eal: fix compile error in eal_timer.c Yi Lu
2016-01-04  9:01 ` David Marchand
2016-01-28 14:16 ` [dpdk-dev] [PATCH] eal: fix compile error in eal_timer.c caused by hpet 卢 毅
2016-03-02 16:45   ` Thomas Monjalon [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=5302405.qOPCxYW0H8@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=luyi68@live.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).