From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: eric.dumazet@gmail.com, dave.taht@gmail.com,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 0/3] netfilter: ecn match fixes and IPv6 capable xtables port
Date: Thu, 09 Jun 2011 15:21:18 +0200 [thread overview]
Message-ID: <4DF0C8CE.1050308@trash.net> (raw)
In-Reply-To: <alpine.LNX.2.01.1106091515160.22244@frira.zrqbmnf.qr>
On 09.06.2011 15:16, Jan Engelhardt wrote:
> On Thursday 2011-06-09 14:12, kaber@trash.net wrote:
>
>> These patches contain two fixes for the ipt_ecn match and an IPv6 capable
>> xtables port. Nothing particulary exciting in the patches, if noone spots
>> any problems I'll push the first two patches to net-2.6 and the third one
>> to net-next-2.6.
>>
>> iptables patch will follow shortly.
>>
>> Patrick McHardy (3):
>> netfilter: ipt_ecn: fix protocol check in ecn_mt_check()
>> netfilter: ipt_ecn: fix inversion for IP header ECN match
>> netfilter: xtables: add an IPv6 capable version of the ECN match
>
> Do you have these in a git:// tree handy? I would like to see if the
> automatic move detection still kicks in (since it has a 50% threshold).
> The raw non-move change could have been split otherwise.
>
I pushed them out to
git://git.kernel.org/pub/scm/linux/kernel/git/kaber/nf-next-testing.git
next prev parent reply other threads:[~2011-06-09 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 12:12 [PATCH 0/3] netfilter: ecn match fixes and IPv6 capable xtables port kaber
2011-06-09 12:12 ` [PATCH 1/3] netfilter: ipt_ecn: fix protocol check in ecn_mt_check() kaber
2011-06-09 12:12 ` [PATCH 2/3] netfilter: ipt_ecn: fix inversion for IP header ECN match kaber
2011-06-09 12:12 ` [PATCH 3/3] netfilter: xtables: add an IPv6 capable version of the " kaber
2011-06-09 13:16 ` [PATCH 0/3] netfilter: ecn match fixes and IPv6 capable xtables port Jan Engelhardt
2011-06-09 13:21 ` Patrick McHardy [this message]
2011-06-09 20:19 ` Jan Engelhardt
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=4DF0C8CE.1050308@trash.net \
--to=kaber@trash.net \
--cc=dave.taht@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.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).