From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@vger.kernel.org,
Patrick McHardy <kaber@trash.net>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH 0/6] ipset patches against net-next-2.6/nf-next-2.6
Date: Thu, 26 May 2011 18:59:34 +0200 [thread overview]
Message-ID: <4DDE86F6.9090901@netfilter.org> (raw)
In-Reply-To: <1305917980-14567-1-git-send-email-kadlec@blackhole.kfki.hu>
On 20/05/11 20:59, Jozsef Kadlecsik wrote:
> Hi Dave and Patrick,
>
> And here are the patches against net-next-2.6 and nf-next-2.6. Patrick,
> the patches can be applied only if nf-next-2.6 is rebased onto current
> net-next-2.6, sorry.
>
> Please consider applying them.
I have applied all of these to my nf-next-2.6 tree.
http://1984.lsi.us.es/git/?p=net-next-2.6/.git;a=shortlog;h=refs/heads/pablo/nf-next-2.6-updates
prev parent reply other threads:[~2011-05-26 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 18:59 [PATCH 0/6] ipset patches against net-next-2.6/nf-next-2.6 Jozsef Kadlecsik
2011-05-20 18:59 ` [PATCH 1/6] netfilter: ipset: Timeout can be modified for already added elements Jozsef Kadlecsik
2011-05-20 18:59 ` [PATCH 2/6] netfilter: ipset: Options and flags support added to the kernel API Jozsef Kadlecsik
2011-05-20 18:59 ` [PATCH 3/6] netfilter: ipset: Support listing setnames and headers too Jozsef Kadlecsik
2011-05-20 18:59 ` [PATCH 4/6] netfilter: ipset: Fix adding ranges to hash types Jozsef Kadlecsik
2011-05-20 18:59 ` [PATCH 5/6] netfilter: ipset: Set type support with multiple revisions added Jozsef Kadlecsik
2011-05-20 18:59 ` [PATCH 6/6] netfilter: ipset: Support range for IPv4 at adding/deleting elements for hash:*net* types Jozsef Kadlecsik
2011-05-26 16:59 ` Pablo Neira Ayuso [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=4DDE86F6.9090901@netfilter.org \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--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).