From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Simon Horman <horms@verge.net.au>, Julian Anastasov <ja@ssi.bg>
Cc: netdev@vger.kernel.org, Patrick McHardy <kaber@trash.net>,
Hans Schillstrom <hans@schillstrom.com>,
LVS devel <lvs-devel@vger.kernel.org>,
Wensong Zhang <wensong@linux-vs.org>,
netfilter-devel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH 0/3] ipvs: IPv6 fragment handling for IPVS
Date: Tue, 21 Aug 2012 09:51:27 +0200 [thread overview]
Message-ID: <1345535487.3069.281.camel@localhost> (raw)
In-Reply-To: <20120821052415.GD14933@verge.net.au>
On Tue, 2012-08-21 at 14:24 +0900, Simon Horman wrote:
> I have no objection to these changes, but I would be more comfortable
> applying them after a review from Hans, Julian or Pablo.
>
I would appreciate a review, especially from Julian.
I'm going to do some more extensive testing on the patchset, in this
week. So, no hurry on applying these, we have time for a good review
process.
next prev parent reply other threads:[~2012-08-21 7:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 13:08 [PATCH 0/3] ipvs: IPv6 fragment handling for IPVS Jesper Dangaard Brouer
2012-08-20 13:08 ` [PATCH 1/3] ipvs: Trivial changes, use compressed IPv6 address in output Jesper Dangaard Brouer
2012-08-20 13:08 ` [PATCH 2/3] ipvs: Fix faulty IPv6 extension header handling in IPVS Jesper Dangaard Brouer
2012-08-21 14:14 ` Julian Anastasov
2012-08-23 12:50 ` Jesper Dangaard Brouer
2012-08-23 16:06 ` Julian Anastasov
2012-08-26 21:13 ` Patrick McHardy
2012-09-04 21:25 ` Jesper Dangaard Brouer
2012-08-20 13:08 ` [PATCH 3/3] ipvs: Complete IPv6 fragment handling for IPVS Jesper Dangaard Brouer
2012-08-21 5:24 ` [PATCH 0/3] ipvs: " Simon Horman
2012-08-21 7:51 ` Jesper Dangaard Brouer [this message]
2012-08-22 6:42 ` 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=1345535487.3069.281.camel@localhost \
--to=brouer@redhat.com \
--cc=hans@schillstrom.com \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=kaber@trash.net \
--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).