From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Simon Horman <horms@verge.net.au>
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: [PATCH] ipvs: fix sparse warnings reported by kbuild test robot
Date: Wed, 17 Apr 2013 14:07:12 +0200 [thread overview]
Message-ID: <20130417120712.GA4177@localhost> (raw)
In-Reply-To: <1366165082-11156-2-git-send-email-horms@verge.net.au>
Hi,
On Wed, Apr 17, 2013 at 11:18:02AM +0900, Simon Horman wrote:
> From: Julian Anastasov <ja@ssi.bg>
>
> Some are from recent commits. Add comments
> that we provide both netmask and prefix len in svc
> netmask.
OK, all these changes have in common that they are mostly fixing
sparse warnings, but these need to be split into several patches
including a description of what that is fixing.
I want these fixes in my tree, but this has to be done in a better
way
Please, resubmit.
prev parent reply other threads:[~2013-04-17 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 2:18 [GIT PULL nf-next] IPVS fixes for v3.10 Simon Horman
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 [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=20130417120712.GA4177@localhost \
--to=pablo@netfilter.org \
--cc=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=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).