From: "Julius Volz" <juliusv@google.com>
To: "Jason Stubbs" <j.stubbs@linkthink.co.jp>
Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Move IPVS from net/ipv4/ipvs to net/netfilter/ipvs in preparation for IPv6 support
Date: Fri, 9 May 2008 15:47:30 +0200 [thread overview]
Message-ID: <f4845fc0805090647j64ec5555i46e4af3269db773d@mail.gmail.com> (raw)
In-Reply-To: <200805092221.57251.j.stubbs@linkthink.co.jp>
On Fri, May 9, 2008, Jason Stubbs wrote:
> I haven't applied the patch and done a diff to individual files to be certain, but I'm pretty sure that the patch is mainly just a directory change.
Yes, this is only a directory move of the current code in the kernel
(with the needed small Kconfig and Makefile adjustments for that, of
course).
Basically, you can arrive at this patch by doing:
$ git mv net/ipv4/ipvs net/netfilter
change net/ipv4/Kconfig:
- source "net/ipv4/ipvs/Kconfig" => move (with adjusted dir)
to net/netfilter/Kconfig
change net/ipv4/Makefile:
- obj-$(CONFIG_IP_VS) += ipvs/ => move to net/netfilter/Makefile
Julius
--
Google Switzerland GmbH
next prev parent reply other threads:[~2008-05-09 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 14:32 [PATCH] Move IPVS from net/ipv4/ipvs to net/netfilter/ipvs in preparation for IPv6 support Julius Volz
2008-05-07 15:00 ` Joseph Mack NA3T
2008-05-07 15:51 ` Julius Volz
2008-05-09 12:49 ` Joseph Mack NA3T
2008-05-09 13:21 ` Jason Stubbs
2008-05-09 13:47 ` Julius Volz [this message]
2008-05-09 13:46 ` Julius Volz
-- strict thread matches above, loose matches on Subject: below --
2008-04-04 10:40 Julius Volz
2008-04-05 1:07 ` Simon Horman
2008-04-05 10:17 ` Julius Volz
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=f4845fc0805090647j64ec5555i46e4af3269db773d@mail.gmail.com \
--to=juliusv@google.com \
--cc=j.stubbs@linkthink.co.jp \
--cc=lvs-devel@vger.kernel.org \
--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).