From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Cc: david.marchand@6wind.com
Subject: Re: [dpdk-dev] [PATCH] eal/linux: fix build with glibc < 2.12
Date: Mon, 20 Jun 2016 10:51:09 +0200 [thread overview]
Message-ID: <6539027.NpQN8fbFNe@xps13> (raw)
In-Reply-To: <1466370670-20981-1-git-send-email-thomas.monjalon@6wind.com>
2016-06-19 23:11, Thomas Monjalon:
> The function rte_thread_setname needs glibc 2.12,
> otherwise it returns -1 without using any parameter.
> The macro RTE_SET_USED avoids an "unused parameter" warning.
>
> Fixes: 3901ed99c2f8 ("eal: fix thread naming on FreeBSD")
>
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
Applied
prev parent reply other threads:[~2016-06-20 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 15:25 [dpdk-dev] [PATCH] eal: fix thread naming on FreeBSD Thomas Monjalon
2016-06-17 15:56 ` David Marchand
2016-06-17 16:02 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2016-06-17 16:04 ` David Marchand
2016-06-17 16:04 ` Thomas Monjalon
2016-06-19 21:11 ` [dpdk-dev] [PATCH] eal/linux: fix build with glibc < 2.12 Thomas Monjalon
2016-06-20 8:51 ` 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=6539027.NpQN8fbFNe@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.marchand@6wind.com \
--cc=dev@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).