From: Stephen Hemminger <shemming@brocade.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] test_mp_secondary??
Date: Wed, 18 Feb 2015 13:17:22 -0800 [thread overview]
Message-ID: <20150218131722.4d4352d6@urahara> (raw)
Why is test_mp_secondary in export list for eal?
$ git grep test_mp_secondary
MAINTAINERS:F: app/test/test_mp_secondary.c
app/test/Makefile:SRCS-y += test_mp_secondary.c
app/test/test.c: { "run_secondary_instances", test_mp_secondary },
app/test/test.h:int test_mp_secondary(void);
app/test/test_mp_secondary.c:test_mp_secondary(void)
app/test/test_mp_secondary.c: .callback = test_mp_secondary,
lib/librte_eal/bsdapp/eal/rte_eal_version.map: test_mp_secondary;
lib/librte_eal/linuxapp/eal/rte_eal_version.map: test_mp_secondary;
reply other threads:[~2015-02-18 21:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150218131722.4d4352d6@urahara \
--to=shemming@brocade.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.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).