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,
lvs-devel@vger.kernel.org
Subject: Re: [PATCH] ipvs: A couple of fixes and cleanups
Date: Mon, 11 Aug 2008 22:57:51 +1000 [thread overview]
Message-ID: <20080811125749.GC19965@verge.net.au> (raw)
In-Reply-To: <alpine.LNX.1.10.0808111416350.12259@titan.stealer.net>
On Mon, Aug 11, 2008 at 02:19:47PM +0200, Sven Wegener wrote:
> On Sun, 10 Aug 2008, Sven Wegener wrote:
>
> > On Sun, 10 Aug 2008, sven.wegener@stealer.net wrote:
> >
> > > Hi guys,
> > >
> > > here come a couple of fixes and cleanups for IPVS. Worth mentioning are the two
> > > possible deadlock fixes. One introduced by my last sync daemon work, which
> > > hasn't hit any stable kernel yet. The other one is in the estimator code and
> > > goes back to at leat since we started working with git for the kernel. The
> > > latter I think qualifies for -stable.
> > >
> > > I've pushed the changes (8123b42..2e45552) based on davem's net tree here
> > >
> > > git://git.stealer.net/linux-2.6.git stealer/ipvs/for-davem
> >
> > I've included the register_ip_vs_protocol() annotation. Changes are now
> > 8123b42..7ead17b. Diffstat has changed slightly, but is probably not worth
> > posting again.
>
> OK, this should be final now. I've pushed the changes 8123b42..e93615d to
>
> git://git.stealer.net/linux-2.6.git stealer/ipvs/for-davem
>
> Simon, as you see I've included your patch and added your acked-by onto
> the other patches.
Thanks. Everything looks in order to me.
prev parent reply other threads:[~2008-08-11 12:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 11:07 [PATCH] ipvs: A couple of fixes and cleanups sven.wegener
2008-08-10 11:07 ` [PATCH 1/9] ipvs: Fix possible deadlock in sync code sven.wegener
2008-08-10 11:07 ` [PATCH 2/9] ipvs: Fix possible deadlock in estimator code sven.wegener
2008-08-10 13:58 ` Sven Wegener
2008-08-10 11:07 ` [PATCH 3/9] ipvs: Use ARRAY_SIZE() sven.wegener
2008-08-10 11:07 ` [PATCH 4/9] ipvs: Use list_empty() instead of open-coding the same functionality sven.wegener
2008-08-10 11:07 ` [PATCH 5/9] ipvs: Initialize schedulers' struct list_head at compile time sven.wegener
2008-08-10 11:07 ` [PATCH 6/9] ipvs: Annotate init functions with __init sven.wegener
2008-08-10 18:32 ` Sven Wegener
2008-08-10 11:07 ` [PATCH 7/9] ipvs: Mark net_vs_ctl_path const sven.wegener
2008-08-10 11:07 ` [PATCH 8/9] ipvs: Embed estimator object into stats object sven.wegener
2008-08-11 12:16 ` Sven Wegener
2008-08-10 11:07 ` [PATCH 9/9] ipvs: No need to zero out ip_vs_stats during initialization sven.wegener
2008-08-10 18:35 ` [PATCH] ipvs: A couple of fixes and cleanups Sven Wegener
2008-08-11 0:50 ` Simon Horman
2008-08-11 6:43 ` Sven Wegener
2008-08-11 6:56 ` Simon Horman
2008-08-11 7:19 ` Simon Horman
2008-08-11 8:19 ` Sven Wegener
2008-08-11 9:31 ` Simon Horman
2008-08-11 12:19 ` Sven Wegener
2008-08-11 12:57 ` Simon Horman [this message]
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=20080811125749.GC19965@verge.net.au \
--to=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--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).