From: Simon Horman <horms@verge.net.au>
To: Sven Wegener <sven.wegener@stealer.net>
Cc: wensong@linux-vs.org, ja@ssi.bg, netdev@vger.kernel.org,
David Miller <davem@davemloft.net>
Subject: Re: [PATCHv2] ipvs: Cleanup sync daemon code
Date: Thu, 17 Jul 2008 12:48:50 +1000 [thread overview]
Message-ID: <20080717024848.GC23699@verge.net.au> (raw)
In-Reply-To: <alpine.LNX.1.10.0807170004580.17284@titan.stealer.net>
On Thu, Jul 17, 2008 at 01:33:44AM +0200, Sven Wegener wrote:
> On Mon, 30 Jun 2008, Simon Horman wrote:
>
> > On Sun, Jun 29, 2008 at 07:32:41PM +0200, Sven Wegener wrote:
> > > It's been a while since my last post of this patch series, but here we go gain.
> > >
> > > Changes since last post:
> > > - Dropped the master daemon sleep change for now, that needs some more work.
> > > - Splitted up the patch into a couple of logical chunks.
> > >
> > > The patches are
> > >
> > > Sven Wegener (5):
> > > ipvs: Initialize mcast addr at compile time
> > > ipvs: Use ERR_PTR for returning errors from make_receive_sock() and make_send_sock()
> > > ipvs: Use kthread_run() instead of doing a double-fork via kernel_thread()
> > > ipvs: Put backup thread on mcast socket wait queue
> > > ipvs: Use schedule_timeout_interruptible() instead of msleep_interruptible()
> > >
> > > The overall difstat looks like
> > >
> > > ip_vs_sync.c | 431 +++++++++++++++++++++++------------------------------------
> > > 1 file changed, 172 insertions(+), 259 deletions(-)
> > >
> > > The patches are based on v2.6.26-rc8. If someone wants to pull them, that can
> > > be done from
> > >
> > > git://git.stealer.net/linux-2.6.git stealer/ipvs/sync-daemon-cleanup
> >
> > These patches look good to me.
>
> So, who is going to take these patches? I expect them to go through
> davem's net-next tree, so I've rebased them onto his tree and appended
> your acked-by. The hton -> __constant_hton change is included.
>
> The changes 0b57664..375c6bb are available at
>
> git://git.stealer.net/linux-2.6.git stealer/ipvs/sync-daemon-cleanup-for-next
Thanks, verified, they look good to me :-)
Dave, is there anything I can do to make merging these patches easier for you?
--
Horms
next prev parent reply other threads:[~2008-07-17 2:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 17:32 [PATCHv2] ipvs: Cleanup sync daemon code Sven Wegener
2008-06-29 17:32 ` [PATCH 1/5] ipvs: Initialize mcast addr at compile time Sven Wegener
2008-07-16 22:04 ` Sven Wegener
2008-06-29 17:32 ` [PATCH 2/5] ipvs: Use ERR_PTR for returning errors from make_receive_sock() and make_send_sock() Sven Wegener
2008-06-29 17:32 ` [PATCH 3/5] ipvs: Use kthread_run() instead of doing a double-fork via kernel_thread() Sven Wegener
2008-06-29 17:32 ` [PATCH 4/5] ipvs: Put backup thread on mcast socket wait queue Sven Wegener
2008-06-29 17:32 ` [PATCH 5/5] ipvs: Use schedule_timeout_interruptible() instead of msleep_interruptible() Sven Wegener
2008-06-30 4:51 ` [PATCHv2] ipvs: Cleanup sync daemon code Simon Horman
2008-07-16 23:33 ` Sven Wegener
2008-07-17 2:48 ` Simon Horman [this message]
2008-07-17 2:50 ` David Miller
2008-07-17 3:07 ` David Miller
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=20080717024848.GC23699@verge.net.au \
--to=horms@verge.net.au \
--cc=davem@davemloft.net \
--cc=ja@ssi.bg \
--cc=netdev@vger.kernel.org \
--cc=sven.wegener@stealer.net \
--cc=wensong@linux-vs.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).