From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 00/12] ipset patches against nf-next-2.6, updated again
Date: Thu, 09 Jun 2011 20:41:43 +0200 [thread overview]
Message-ID: <4DF113E7.20105@netfilter.org> (raw)
In-Reply-To: <4DF0F05E.2090406@trash.net>
On 09/06/11 18:10, Patrick McHardy wrote:
> On 01.06.2011 23:35, Jozsef Kadlecsik wrote:
>> Hi Patrick,
>>
>> I have updated the patches with the changes since last time I sent them.
>> The patches can be applied only if nf-next-2.6 is rebased onto current
>> net-next-2.6.
>>
>> Please consider applying them.
>
> Thanks, I'll wait for Pablo to either apply these or submit his pending
> patches so we can avoid any conflicts.
I just send the four patches that I collected. Please take Jozsef's
directly from him.
next prev parent reply other threads:[~2011-06-09 18:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 21:35 [PATCH 00/12] ipset patches against nf-next-2.6, updated again Jozsef Kadlecsik
2011-06-01 21:35 ` [PATCH 01/12] netfilter: ipset: Timeout can be modified for already added elements Jozsef Kadlecsik
2011-06-01 21:35 ` [PATCH 02/12] netfilter: ipset: Options and flags support added to the kernel API Jozsef Kadlecsik
2011-06-01 21:35 ` [PATCH 03/12] netfilter: ipset: Support listing setnames and headers too Jozsef Kadlecsik
2011-06-01 21:35 ` [PATCH 04/12] netfilter: ipset: Fix adding ranges to hash types Jozsef Kadlecsik
2011-06-01 21:35 ` [PATCH 05/12] netfilter: ipset: Set type support with multiple revisions added Jozsef Kadlecsik
2011-06-01 21:35 ` [PATCH 06/12] netfilter: ipset: Support range for IPv4 at adding/deleting elements for hash:*net* types Jozsef Kadlecsik
2011-06-01 21:35 ` [PATCH 07/12] netfilter: ipset: Take into account cidr value for the from address when creating the set Jozsef Kadlecsik
2011-06-01 21:35 ` [PATCH 08/12] netfilter: ipset: Add xt_action_param to the variant level kadt functions Jozsef Kadlecsik
2011-06-01 21:35 ` [PATCH 09/12] netfilter: ipset: Fix return code for destroy when sets are in use Jozsef Kadlecsik
2011-06-01 21:35 ` [PATCH 10/12] netfilter: ipset: Use the stored first cidr value instead of '1' Jozsef Kadlecsik
2011-06-01 21:35 ` [PATCH 11/12] netfilter: ipset: hash:net,iface type introduced Jozsef Kadlecsik
2011-06-01 21:35 ` [PATCH 12/12] netfilter: ipset: Whitespace and coding fixes, detected by checkpatch.pl Jozsef Kadlecsik
2011-06-02 12:57 ` Pablo Neira Ayuso
2011-06-02 12:57 ` [PATCH 11/12] netfilter: ipset: hash:net,iface type introduced Pablo Neira Ayuso
2011-06-02 12:56 ` [PATCH 10/12] netfilter: ipset: Use the stored first cidr value instead of '1' Pablo Neira Ayuso
2011-06-02 12:56 ` [PATCH 09/12] netfilter: ipset: Fix return code for destroy when sets are in use Pablo Neira Ayuso
2011-06-02 12:56 ` [PATCH 08/12] netfilter: ipset: Add xt_action_param to the variant level kadt functions Pablo Neira Ayuso
2011-06-02 12:31 ` [PATCH 00/12] ipset patches against nf-next-2.6, updated again Pablo Neira Ayuso
2011-06-09 16:10 ` Patrick McHardy
2011-06-09 18:41 ` Pablo Neira Ayuso [this message]
2011-06-11 14:57 ` Jozsef Kadlecsik
2011-06-16 14:57 ` Patrick McHardy
2011-06-16 15:04 ` Patrick McHardy
2011-06-16 16:15 ` Jozsef Kadlecsik
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=4DF113E7.20105@netfilter.org \
--to=pablo@netfilter.org \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--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).