From: Ravi Kerur <rkerur@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 0/6] Move EAL common functions
Date: Sat, 27 Dec 2014 10:32:02 -0500 [thread overview]
Message-ID: <1419694322-2114-1-git-send-email-rkerur@gmail.com> (raw)
Fix Neil's patch review comments.
Common functions in linuxapp and bsdapp are moved into
librte_eal/common directory.
New files added follow _common_ naming conventions.
Following checkpatch warnings are treated as false-positive.
1. WARNING: quoted string split across lines
Tested against ubuntu and FreeBSD.
Ravi Kerur (6):
Move EAL common functions
Move EAL common functions
Move EAL common functions
Move EAL common functions
Move EAL common functions
Move EAL common functions
app/test/test_debug.c | 1 -
lib/librte_eal/bsdapp/eal/Makefile | 11 +-
lib/librte_eal/bsdapp/eal/eal.c | 233 +--------------------
lib/librte_eal/bsdapp/eal/eal_debug.c | 113 -----------
lib/librte_eal/bsdapp/eal/eal_lcore.c | 62 ++----
lib/librte_eal/bsdapp/eal/eal_memory.c | 40 +---
lib/librte_eal/bsdapp/eal/eal_thread.c | 233 ---------------------
lib/librte_eal/bsdapp/eal/eal_timer.c | 50 +----
lib/librte_eal/common/eal_common.c | 326 ++++++++++++++++++++++++++++++
lib/librte_eal/common/eal_common_debug.c | 106 ++++++++++
lib/librte_eal/common/eal_common_lcore.c | 106 ++++++++++
lib/librte_eal/common/eal_common_memory.c | 38 +++-
lib/librte_eal/common/eal_common_thread.c | 248 +++++++++++++++++++++++
lib/librte_eal/common/eal_common_timer.c | 95 +++++++++
lib/librte_eal/common/eal_externs.h | 45 +++++
lib/librte_eal/common/eal_hugepages.h | 1 +
lib/librte_eal/common/eal_private.h | 112 ++++++++++
lib/librte_eal/common/include/rte_debug.h | 7 -
lib/librte_eal/linuxapp/eal/Makefile | 11 +-
lib/librte_eal/linuxapp/eal/eal.c | 246 +---------------------
lib/librte_eal/linuxapp/eal/eal_debug.c | 113 -----------
lib/librte_eal/linuxapp/eal/eal_lcore.c | 55 +----
lib/librte_eal/linuxapp/eal/eal_memory.c | 36 +---
lib/librte_eal/linuxapp/eal/eal_thread.c | 233 ---------------------
lib/librte_eal/linuxapp/eal/eal_timer.c | 54 +----
25 files changed, 1134 insertions(+), 1441 deletions(-)
delete mode 100644 lib/librte_eal/bsdapp/eal/eal_debug.c
delete mode 100644 lib/librte_eal/bsdapp/eal/eal_thread.c
create mode 100644 lib/librte_eal/common/eal_common.c
create mode 100644 lib/librte_eal/common/eal_common_debug.c
create mode 100644 lib/librte_eal/common/eal_common_lcore.c
create mode 100644 lib/librte_eal/common/eal_common_thread.c
create mode 100644 lib/librte_eal/common/eal_common_timer.c
create mode 100644 lib/librte_eal/common/eal_externs.h
delete mode 100644 lib/librte_eal/linuxapp/eal/eal_debug.c
delete mode 100644 lib/librte_eal/linuxapp/eal/eal_thread.c
--
1.9.1
next reply other threads:[~2014-12-27 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 15:32 Ravi Kerur [this message]
2014-12-27 15:33 ` [dpdk-dev] [PATCH v2 1/6] " Ravi Kerur
2014-12-27 15:33 ` [dpdk-dev] [PATCH v2 2/6] " Ravi Kerur
2014-12-27 15:33 ` [dpdk-dev] [PATCH v2 3/6] " Ravi Kerur
2014-12-27 15:33 ` [dpdk-dev] [PATCH v2 4/6] " Ravi Kerur
2014-12-27 15:33 ` [dpdk-dev] [PATCH v2 5/6] " Ravi Kerur
2014-12-27 15:33 ` [dpdk-dev] [PATCH v2 6/6] " Ravi Kerur
2014-12-28 20:42 ` [dpdk-dev] [PATCH v2 1/6] " Neil Horman
2014-12-29 15:34 ` Ravi Kerur
2014-12-29 16:18 ` 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=1419694322-2114-1-git-send-email-rkerur@gmail.com \
--to=rkerur@gmail.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).