From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 0/7] ipset patches against net-next-2.6/nf-next-2.6, updated
Date: Thu, 26 May 2011 19:17:54 +0200 [thread overview]
Message-ID: <4DDE8B42.8020804@trash.net> (raw)
In-Reply-To: <4DDE8A8E.9090507@netfilter.org>
Am 26.05.2011 19:14, schrieb Pablo Neira Ayuso:
> On 24/05/11 10:22, Jozsef Kadlecsik wrote:
>> Hi Patrick,
>>
>> And here are the updated patches against net-next-2.6 and nf-next-2.6.
>> The patches can be applied only if nf-next-2.6 is rebased onto current
>> net-next-2.6, sorry.
>>
>> Please consider applying them.
>
> OK, I have taken these, and removed those that you sent on Friday 20th May.
>
I'll add them to my tree as well, but until -rc1 is out there's no new
features :)
prev parent reply other threads:[~2011-05-26 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 8:22 [PATCH 0/7] ipset patches against net-next-2.6/nf-next-2.6, updated Jozsef Kadlecsik
2011-05-24 8:22 ` [PATCH 1/7] netfilter: ipset: Timeout can be modified for already added elements Jozsef Kadlecsik
2011-05-24 8:22 ` [PATCH 2/7] netfilter: ipset: Options and flags support added to the kernel API Jozsef Kadlecsik
2011-05-24 8:22 ` [PATCH 3/7] netfilter: ipset: Support listing setnames and headers too Jozsef Kadlecsik
2011-05-24 8:22 ` [PATCH 4/7] netfilter: ipset: Fix adding ranges to hash types Jozsef Kadlecsik
2011-05-24 8:22 ` [PATCH 5/7] netfilter: ipset: Set type support with multiple revisions added Jozsef Kadlecsik
2011-05-24 8:22 ` [PATCH 6/7] netfilter: ipset: Support range for IPv4 at adding/deleting elements for hash:*net* types Jozsef Kadlecsik
2011-05-24 8:22 ` [PATCH 7/7] netfilter: ipset: Take into account cidr value for the from address when creating the set Jozsef Kadlecsik
2011-05-26 17:14 ` [PATCH 0/7] ipset patches against net-next-2.6/nf-next-2.6, updated Pablo Neira Ayuso
2011-05-26 17:17 ` Patrick McHardy [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=4DDE8B42.8020804@trash.net \
--to=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--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).