From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Simon Horman <horms@verge.net.au>
Cc: Julian Anastasov <ja@ssi.bg>, Alex Gartrell <agartrell@fb.com>,
netdev@vger.kernel.org, lvs-devel@vger.kernel.org,
kernel-team@fb.com, ps@fb.com, David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next 00/20] Support v6 real servers in v4 pools and vice versa
Date: Wed, 10 Sep 2014 17:16:17 +0200 [thread overview]
Message-ID: <20140910151617.GA4830@salvia> (raw)
In-Reply-To: <20140910062201.GA11468@verge.net.au>
On Wed, Sep 10, 2014 at 03:22:01PM +0900, Simon Horman wrote:
> [ CC Pablo, Dave M ]
>
> On Wed, Sep 10, 2014 at 09:01:34AM +0300, Julian Anastasov wrote:
> >
> > Hello,
> >
> > On Tue, 9 Sep 2014, Alex Gartrell wrote:
> >
> > > The following patch set has been iterated upon in the lvs-devel mailing
> > > list. I am submitting it here per Julian's advice for inclusion in the
> > > net-next tree.
> >
> > Acked-by: Julian Anastasov <ja@ssi.bg>
> >
> > Simon, please apply the patchset to ipvs-next.
> > I guess ipvs-next and nf-next need to be updated
> > before that due to dependency on net-next commit ea1d5d7755a3e556
> > ("ipvs: properly declare tunnel encapsulation").
>
> Thanks Julian, yes that does seem to be the case.
>
> Pablo, could you merge nf into nf-next and push the result
> so that I can apply this series on top?
Let me flush out my nf-next queue first, many updates in it, I'll ping
to let you know once you can prepare your series. Thanks.
next prev parent reply other threads:[~2014-09-10 15:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 23:40 [PATCH net-next 00/20] Support v6 real servers in v4 pools and vice versa Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 01/20] ipvs: Add destination address family to netlink interface Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 02/20] ipvs: Supply destination addr family to ip_vs_{lookup_dest,find_dest} Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 03/20] ipvs: Pass destination address family to ip_vs_trash_get_dest Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 04/20] ipvs: Supply destination address family to ip_vs_conn_new Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 05/20] ipvs: prevent mixing heterogeneous pools and synchronization Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 06/20] ipvs: Pull out crosses_local_route_boundary logic Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 07/20] ipvs: Pull out update_pmtu code Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 08/20] ipvs: Add generic ensure_mtu_is_adequate to handle mixed pools Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 09/20] ipvs: support ipv4 in ipv6 and ipv6 in ipv4 tunnel forwarding Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 10/20] ipvs: address family of LBLC entry depends on svc family Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 11/20] ipvs: address family of LBLCR " Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 12/20] ipvs: use correct address family in DH logs Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 13/20] ipvs: use correct address family in LC logs Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 14/20] ipvs: use correct address family in NQ logs Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 15/20] ipvs: use correct address family in RR logs Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 16/20] ipvs: use correct address family in SED logs Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 17/20] ipvs: use correct address family in SH logs Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 18/20] ipvs: use correct address family in WLC logs Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 19/20] ipvs: use the new dest addr family field Alex Gartrell
2014-09-09 23:40 ` [PATCH net-next 20/20] ipvs: Allow heterogeneous pools now that we support them Alex Gartrell
2014-09-10 6:01 ` [PATCH net-next 00/20] Support v6 real servers in v4 pools and vice versa Julian Anastasov
2014-09-10 6:22 ` Simon Horman
2014-09-10 15:16 ` Pablo Neira Ayuso [this message]
2014-09-10 23:55 ` 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=20140910151617.GA4830@salvia \
--to=pablo@netfilter.org \
--cc=agartrell@fb.com \
--cc=davem@davemloft.net \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=kernel-team@fb.com \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ps@fb.com \
/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).