From: Cong Wang <xiyou.wangcong@gmail.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
WANG Cong <xiyou.wangcong@gmail.com>
Subject: [Patch] net: move ifenslave from Documentation/networking to tools/networking
Date: Wed, 1 Feb 2012 17:09:02 +0800 [thread overview]
Message-ID: <1328087342-24721-1-git-send-email-xiyou.wangcong@gmail.com> (raw)
ifenslave is a real tool, and it seems main distros already ship this.
It is nice to move it to tools/networking/ directory.
(Note that this patch is generated by 'git diff -C', in case of having
a large patch.)
Cc: "David S. Miller" <davem@davemloft.net>
Signed-off-by: WANG Cong <xiyou.wangcong@gmail.com>
---
Documentation/networking/Makefile | 8 --------
tools/networking/Makefile | 11 +++++++++++
{Documentation => tools}/networking/ifenslave.c | 0
3 files changed, 11 insertions(+), 8 deletions(-)
diff --git a/Documentation/networking/Makefile b/Documentation/networking/Makefile
index 24c308d..7284363 100644
--- a/Documentation/networking/Makefile
+++ b/Documentation/networking/Makefile
@@ -1,12 +1,4 @@
# kbuild trick to avoid linker error. Can be omitted if a module is built.
obj- := dummy.o
-# List of programs to build
-hostprogs-y := ifenslave
-
-HOSTCFLAGS_ifenslave.o += -I$(objtree)/usr/include
-
-# Tell kbuild to always build the programs
-always := $(hostprogs-y)
-
obj-m := timestamping/
diff --git a/tools/networking/Makefile b/tools/networking/Makefile
new file mode 100644
index 0000000..ccc1df9
--- /dev/null
+++ b/tools/networking/Makefile
@@ -0,0 +1,11 @@
+
+CC := $(CROSS_COMPILE)gcc
+CFLAGS := -Wall -Wstrict-prototypes
+RM := rm -f
+
+all: ifenslave
+ifenslave: ifenslave.c
+ $(CC) $(CFLAGS) -o $@ $^
+clean:
+ $(RM) ifenslave
+
diff --git a/Documentation/networking/ifenslave.c b/tools/networking/ifenslave.c
similarity index 100%
rename from Documentation/networking/ifenslave.c
rename to tools/networking/ifenslave.c
reply other threads:[~2012-02-01 9:09 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=1328087342-24721-1-git-send-email-xiyou.wangcong@gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).