From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Liang, Cunming" <cunming.liang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH v1 0/2] eal: fix symbol missing in version map
Date: Wed, 25 Feb 2015 10:07:15 +0100 [thread overview]
Message-ID: <4305328.RvZUiQGGu0@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2EC7A74-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
> > These two patches are the fixing for the compling error when
> > CONFIG_RTE_BUILD_SHARED_LIB=y.
> > The root cause is *per_lcore__socket_id* and *rte_sys_gettid* are missing
> > in the version map.
> > Thanks for the notification from Tetsuya Mukawa <mukawa-AlSX/UN32fvPDbFq/vQRIQ@public.gmane.org>.
Please use Reported-by: in such case.
Fixes: ef76436c6834 ("eal: get unique thread id")
Fixes: 9e29251b2afa ("eal: thread affinity API")
> > Cunming Liang (2):
> > eal/linux: fix symbol missing in version map
> > eal/bsd: fix symbol missing in version map
Merged together
> Series Acked-by: John McNamara <john.mcnamara-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Applied, thanks
next prev parent reply other threads:[~2015-02-25 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 3:39 [PATCH v1 0/2] eal: fix symbol missing in version map Cunming Liang
[not found] ` <1424835589-18122-1-git-send-email-cunming.liang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-02-25 3:39 ` [PATCH v1 1/2] eal/linux: " Cunming Liang
2015-02-25 3:39 ` [PATCH v1 2/2] eal/bsd: " Cunming Liang
2015-02-25 4:08 ` [PATCH v1 0/2] eal: " Tetsuya Mukawa
2015-02-25 8:14 ` Mcnamara, John
[not found] ` <B27915DBBA3421428155699D51E4CFE2EC7A74-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-02-25 9:07 ` Thomas Monjalon [this message]
2015-02-25 12:30 ` Neil Horman
[not found] ` <20150225123053.GA31224-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2015-02-25 13:39 ` Thomas Monjalon
2015-02-25 14:34 ` Neil Horman
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=4305328.RvZUiQGGu0@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=cunming.liang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.