From: Ravi Kerur <rkerur@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH 0/2] [RFC] Moving EAL source files into common dir.
Date: Tue, 16 Dec 2014 10:52:04 -0800 [thread overview]
Message-ID: <CAFb4SLBO50GSPHnYxC2mPNajXfzuAdzYtWAjSoYVFmJfa4W3Dg@mail.gmail.com> (raw)
This patch is RFC for moving EAL source files into common directory.
Currently eal_alarm.c, eal_interrupts.c and eal_debug.c are moved.
Please let me know if this approach makes sense.
Ravi Kerur (2):
Move EAL source files into common directory.
Makefile changes for moved files.
lib/librte_eal/bsdapp/eal/Makefile | 6 +-
lib/librte_eal/bsdapp/eal/eal_alarm.c | 60 --
lib/librte_eal/bsdapp/eal/eal_debug.c | 113 ----
lib/librte_eal/bsdapp/eal/eal_interrupts.c | 71 ---
lib/librte_eal/common/eal_common_alarm.c | 308 +++++++++
lib/librte_eal/common/eal_common_debug.c | 113 ++++
lib/librte_eal/common/eal_common_interrupts.c | 869
++++++++++++++++++++++++++
lib/librte_eal/common/eal_vfio.h | 55 ++
lib/librte_eal/linuxapp/eal/Makefile | 6 +-
lib/librte_eal/linuxapp/eal/eal_alarm.c | 268 --------
lib/librte_eal/linuxapp/eal/eal_debug.c | 113 ----
lib/librte_eal/linuxapp/eal/eal_interrupts.c | 826
------------------------
lib/librte_eal/linuxapp/eal/eal_vfio.h | 55 --
13 files changed, 1351 insertions(+), 1512 deletions(-) delete mode
100644 lib/librte_eal/bsdapp/eal/eal_alarm.c
delete mode 100644 lib/librte_eal/bsdapp/eal/eal_debug.c
delete mode 100644 lib/librte_eal/bsdapp/eal/eal_interrupts.c
create mode 100644 lib/librte_eal/common/eal_common_alarm.c
create mode 100644 lib/librte_eal/common/eal_common_debug.c
create mode 100644 lib/librte_eal/common/eal_common_interrupts.c
create mode 100644 lib/librte_eal/common/eal_vfio.h delete mode 100644
lib/librte_eal/linuxapp/eal/eal_alarm.c
delete mode 100644 lib/librte_eal/linuxapp/eal/eal_debug.c
delete mode 100644 lib/librte_eal/linuxapp/eal/eal_interrupts.c
delete mode 100644 lib/librte_eal/linuxapp/eal/eal_vfio.h
--
1.9.1
reply other threads:[~2014-12-16 18:52 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=CAFb4SLBO50GSPHnYxC2mPNajXfzuAdzYtWAjSoYVFmJfa4W3Dg@mail.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).