netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Simon Horman <horms@verge.net.au>,
	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>,
	Hans Schillstrom <hans.schillstrom@ericsson.com>,
	Hans Schillstrom <hans@schillstrom.com>
Subject: Re: [GIT PULL nf-next] IPVS for 3.7 #2
Date: Mon, 22 Oct 2012 13:53:50 +0200	[thread overview]
Message-ID: <1350906830.22194.451.camel@localhost> (raw)
In-Reply-To: <20121022105557.GA16283@1984>

On Mon, 2012-10-22 at 12:55 +0200, Pablo Neira Ayuso wrote:
> Hi Simon, Jesper,
> 
> On Fri, Sep 28, 2012 at 11:54:57AM +0900, Simon Horman wrote:
> > Hi Pablo,
> > 
> > please consider the following enhancements to IPVS for inclusion in 3.7.
> > 
> > ----------------------------------------------------------------
> > The following changes since commit 82c93fcc2e1737fede2752520f1bf8f4de6304d8:
> > 
> >   x86: bpf_jit_comp: add XOR instruction for BPF JIT (2012-09-24 16:54:35 -0400)
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs-next.git master
> 
> I've pulled this now that net-next is back open.
> 
> Please, next time re-submit again if you miss the merge window.

I did plan to resubmit (incl. with the changes mentioned below)
But thanks a lot for pulling this.

> BTW, I expect one follow-up patch to move ipv6_find_hdr to
> net/ipv6/netfilter.c (so you don't need to depend on ip6_tables for
> just one single function).
> 
> Thanks a lot!

Before finishing this email, Yuanhan Liu <yuanhan.liu(at)intel.com>
kicked by butt, and pointed out a build error, when compiling *without*
CONFIG_IP_VS_IPV6.  I'm really really really sorry for this, I'll
quickly submit a patch fixing this!




      reply	other threads:[~2012-10-22 11:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28  2:54 [GIT PULL nf-next] IPVS for 3.7 #2 Simon Horman
2012-09-28  2:54 ` [PATCH 1/7] ipvs: Trivial changes, use compressed IPv6 address in output Simon Horman
2012-09-28  2:54 ` [PATCH 2/7] ipvs: IPv6 extend ICMPv6 handling for future types Simon Horman
2012-09-28  2:55 ` [PATCH 3/7] ipvs: Use config macro IS_ENABLED() Simon Horman
2012-09-28  2:55 ` [PATCH 4/7] ipvs: Fix faulty IPv6 extension header handling in IPVS Simon Horman
2012-09-28  2:55 ` [PATCH 5/7] ipvs: Complete IPv6 fragment handling for IPVS Simon Horman
2012-09-28  2:55 ` [PATCH 6/7] ipvs: API change to avoid rescan of IPv6 exthdr Simon Horman
2012-09-28  2:55 ` [PATCH 7/7] ipvs: SIP fragment handling Simon Horman
2012-10-08 18:44 ` [GIT PULL nf-next] IPVS for 3.7 #2 Jesper Dangaard Brouer
2012-10-08 23:17   ` Pablo Neira Ayuso
2012-10-09  3:52     ` Simon Horman
2012-10-22 10:55 ` Pablo Neira Ayuso
2012-10-22 11:53   ` Jesper Dangaard Brouer [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=1350906830.22194.451.camel@localhost \
    --to=brouer@redhat.com \
    --cc=hans.schillstrom@ericsson.com \
    --cc=hans@schillstrom.com \
    --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=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).