From: David Miller <davem@davemloft.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/8] IPVS updates for net-next tree
Date: Fri, 26 Oct 2012 14:50:06 -0400 (EDT) [thread overview]
Message-ID: <20121026.145006.1534097522946444293.davem@davemloft.net> (raw)
In-Reply-To: <1351243478-4852-1-git-send-email-pablo@netfilter.org>
From: pablo@netfilter.org
Date: Fri, 26 Oct 2012 11:24:30 +0200
> The following changeset contains updates for IPVS from Jesper Dangaard
> Brouer that did not reach the previous merge window in time.
>
> More specifically, updates to improve IPv6 support in IPVS. More
> relevantly, some of the existing code performed wrong handling of the
> extensions headers and better fragmentation handling.
>
> Jesper promised more follow-up patches to refine this after this batch
> hits net-next. Yet to come.
>
> You can pull these changes from:
>
> git://1984.lsi.us.es/nf-next master
Pulled, thanks.
prev parent reply other threads:[~2012-10-26 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 9:24 [PATCH 0/8] IPVS updates for net-next tree pablo
2012-10-26 9:24 ` [PATCH 1/8] ipvs: Trivial changes, use compressed IPv6 address in output pablo
2012-10-26 9:24 ` [PATCH 2/8] ipvs: IPv6 extend ICMPv6 handling for future types pablo
2012-10-26 9:24 ` [PATCH 3/8] ipvs: Use config macro IS_ENABLED() pablo
2012-10-26 9:24 ` [PATCH 4/8] ipvs: Fix faulty IPv6 extension header handling in IPVS pablo
2012-10-26 9:24 ` [PATCH 5/8] ipvs: Complete IPv6 fragment handling for IPVS pablo
2012-10-26 9:24 ` [PATCH 6/8] ipvs: API change to avoid rescan of IPv6 exthdr pablo
2012-10-26 9:24 ` [PATCH 7/8] ipvs: SIP fragment handling pablo
2012-10-26 9:24 ` [PATCH 8/8] ipvs: fix build errors related to config option combinations pablo
2012-10-26 18:50 ` David Miller [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=20121026.145006.1534097522946444293.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).