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-next] IPVS fixes for v3.10
Date: Wed, 17 Apr 2013 11:18:01 +0900 [thread overview]
Message-ID: <1366165082-11156-1-git-send-email-horms@verge.net.au> (raw)
Hi Pablo,
The following changes since commit aaa795ad25e18488b026572c7ba2ca8f99ced0b7:
netfilter: nat: propagate errors from xfrm_me_harder() (2013-04-08 12:34:01 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs-next.git tags/ipvs3-for-v3.10
for you to fetch changes up to 4208bd136ff6d885982c9581e861577785bf3a98:
ipvs: fix sparse warnings reported by kbuild test robot (2013-04-17 11:01:42 +0900)
----------------------------------------------------------------
Fix from Julian Anastasov for warnings flagged by sparse.
Some problems relate to changes introduced since v3.9. Others
have been around for longer.
----------------------------------------------------------------
Julian Anastasov (1):
ipvs: fix sparse warnings reported by kbuild test robot
include/net/ip_vs.h | 8 +++---
include/uapi/linux/ip_vs.h | 4 +--
net/netfilter/ipvs/ip_vs_conn.c | 14 +++++-----
net/netfilter/ipvs/ip_vs_core.c | 3 ++-
net/netfilter/ipvs/ip_vs_ctl.c | 55 +++++++++++++++++++++++---------------
net/netfilter/ipvs/ip_vs_lblc.c | 2 +-
net/netfilter/ipvs/ip_vs_lblcr.c | 2 +-
net/netfilter/ipvs/ip_vs_sync.c | 4 +--
8 files changed, 52 insertions(+), 40 deletions(-)
next reply other threads:[~2013-04-17 2:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 2:18 Simon Horman [this message]
2013-04-17 2:18 ` [PATCH] ipvs: fix sparse warnings reported by kbuild test robot Simon Horman
2013-04-17 12:07 ` 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=1366165082-11156-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 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).