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: [GIT PULL nf] IPVS fixes for v3.9
Date: Tue, 19 Mar 2013 10:39:55 +0900 [thread overview]
Message-ID: <1363657198-5333-1-git-send-email-horms@verge.net.au> (raw)
Hi Pablo,
The following changes since commit a82783c91d5dce680dbd290ebf301a520b0e72a5:
netfilter: ip6t_NPT: restrict to mangle table (2013-03-15 12:58:21 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs.git tags/ipvs-fixes-for-v3.9
for you to fetch changes up to 1804ac13ac3d9d39b94f3074f303b286e90632ba:
ipvs: fix some sparse warnings (2013-03-19 09:37:37 +0900)
----------------------------------------------------------------
IPVS fixes for v3.9 from Julian Anastasov
----------------------------------------------------------------
Julian Anastasov (3):
ipvs: fix sctp chunk length order
ipvs: fix hashing in ip_vs_svc_hashkey
ipvs: fix some sparse warnings
include/net/ip_vs.h | 2 +-
net/netfilter/ipvs/ip_vs_core.c | 8 +-------
net/netfilter/ipvs/ip_vs_ctl.c | 8 +++++---
net/netfilter/ipvs/ip_vs_est.c | 2 +-
net/netfilter/ipvs/ip_vs_proto_sctp.c | 16 +++++++++-------
5 files changed, 17 insertions(+), 19 deletions(-)
next reply other threads:[~2013-03-19 1:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 1:39 Simon Horman [this message]
2013-03-19 1:39 ` [PATCH 1/3] ipvs: fix sctp chunk length order Simon Horman
2013-03-19 1:39 ` [PATCH 2/3] ipvs: fix hashing in ip_vs_svc_hashkey Simon Horman
2013-03-19 1:39 ` [PATCH 3/3] ipvs: fix some sparse warnings Simon Horman
2013-03-19 9:45 ` [GIT PULL nf] IPVS fixes for v3.9 Pablo Neira Ayuso
2013-03-19 12:15 ` Simon Horman
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=1363657198-5333-1-git-send-email-horms@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.