From: Simon Horman <horms@verge.net.au>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org,
Wensong Zhang <wensong@linux-vs.org>,
Julian Anastasov <ja@ssi.bg>
Subject: Re: [GIT PULL nf-next] IPVS
Date: Tue, 19 Mar 2013 09:38:40 +0900 [thread overview]
Message-ID: <20130319003840.GG15718@verge.net.au> (raw)
In-Reply-To: <20130318233115.GA23070@localhost>
On Tue, Mar 19, 2013 at 12:31:15AM +0100, Pablo Neira Ayuso wrote:
> Hi Simon,
>
> On Mon, Mar 18, 2013 at 10:15:38PM +0900, Simon Horman wrote:
> [...]
> > ----------------------------------------------------------------
> > IPVS enhancements for v3.10 from Julian Anastasov
> >
> > ----------------------------------------------------------------
> > Julian Anastasov (5):
> > ipvs: add backup_only flag to avoid loops
> > ipvs: remove extra rcu lock
> > ipvs: fix sctp chunk length order
> > ipvs: fix hashing in ip_vs_svc_hashkey
> > ipvs: fix some sparse warnings
>
> I think that these three fixes:
>
> ipvs: add backup_only flag to avoid loops
> ipvs: remove extra rcu lock
> ipvs: fix sctp chunk length order
>
> should find their path to the net tree.
>
> The remaining two sparse fixes should go to net-next.
>
> I can manually apply these patch if you want to the corresponding
> trees.
Thanks. I'll send two fresh pull requests shortly.
next prev parent reply other threads:[~2013-03-19 0:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 13:15 [GIT PULL nf-next] IPVS Simon Horman
2013-03-18 13:15 ` [PATCH 1/5] ipvs: add backup_only flag to avoid loops Simon Horman
2013-03-18 13:15 ` [PATCH 2/5] ipvs: remove extra rcu lock Simon Horman
2013-03-18 13:15 ` [PATCH 3/5] ipvs: fix sctp chunk length order Simon Horman
2013-03-18 13:15 ` [PATCH 4/5] ipvs: fix hashing in ip_vs_svc_hashkey Simon Horman
2013-03-18 13:15 ` [PATCH 5/5] ipvs: fix some sparse warnings Simon Horman
2013-03-18 23:31 ` [GIT PULL nf-next] IPVS Pablo Neira Ayuso
2013-03-19 0:38 ` Simon Horman [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-10 1:41 Simon Horman
2012-08-14 9:06 ` Pablo Neira Ayuso
2012-07-23 23:28 Simon Horman
2012-07-23 23:35 ` David Miller
2012-07-24 1:01 ` Simon Horman
2012-07-24 1:11 ` David Miller
2012-07-11 0:25 Simon Horman
2012-03-21 8:56 Simon Horman
2011-12-09 7:13 Simon Horman
2011-12-09 21:13 ` Pablo Neira Ayuso
2011-12-07 8:07 Simon Horman
2011-10-21 1:33 Simon Horman
2011-10-21 7:27 ` Pablo Neira Ayuso
2011-11-07 3:07 ` Simon Horman
2011-11-07 8:29 ` Pablo Neira Ayuso
2011-11-09 0:58 ` Simon Horman
2011-11-09 14:36 ` Pablo Neira Ayuso
2011-11-10 1:22 ` Simon Horman
2011-10-01 3:34 Simon Horman
2011-10-10 23:42 ` Pablo Neira Ayuso
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=20130319003840.GG15718@verge.net.au \
--to=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--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).