netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH 0/8] ipset patches
Date: Tue, 17 Jan 2012 00:08:34 +0100	[thread overview]
Message-ID: <20120116230834.GA18052@1984> (raw)
In-Reply-To: <alpine.DEB.2.00.1201161650330.32599@blackhole.kfki.hu>

On Mon, Jan 16, 2012 at 04:52:21PM +0100, Jozsef Kadlecsik wrote:
> On Mon, 16 Jan 2012, Pablo Neira Ayuso wrote:
> 
> > On Sat, Jan 14, 2012 at 05:38:53PM +0100, Jozsef Kadlecsik wrote:
> > > 
> > > Here follow the patches which bring the kernel in sync with the current
> > > ipset release. I included the patches which was sent in September but was
> > > forgotten due to the kernel.org issues. Please consider applying them.
> > > 
> > > Jan Engelhardt (3):
> > >   netfilter: ipset: use NFPROTO_ constants
> > >   netfilter: ipset: avoid use of kernel-only types
> > >   netfilter: ipset: expose userspace-relevant parts in ip_set.h
> > > 
> > > Jozsef Kadlecsik (5):
> > >   netfilter: ipset: Autoload set type modules safely
> > >   netfilter: ipset: Dumping error triggered removing references twice
> > >   netfilter: ipset: Log warning when a hash type of set gets full
> > >   netfilter: ipset: Exceptions support added to hash:*net* types
> > >   netfilter: ipset: hash:net,iface timeout bug fixed
> > 
> > Thanks Jozsef. I'll take this once. net-next becomes active again
> > (after -rc1 is released).
> > 
> > It would *really* great if you can set some git tree I can pull
> > your changes from.
> 
> Here you are, you can pull the changes from
> 
> 	git://blackhole.kfki.hu/git/net-next ipset

Thanks Jozsef.

I have put these into one ipset branch in my net-next tree. I'll merge
your changes and pass it to davem once net-next becomes active again.

  reply	other threads:[~2012-01-16 23:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-14 16:38 [PATCH 0/8] ipset patches Jozsef Kadlecsik
2012-01-14 16:38 ` [PATCH 1/8] netfilter: ipset: use NFPROTO_ constants Jozsef Kadlecsik
2012-01-14 16:38 ` [PATCH 2/8] netfilter: ipset: avoid use of kernel-only types Jozsef Kadlecsik
2012-01-14 16:38 ` [PATCH 3/8] netfilter: ipset: expose userspace-relevant parts in ip_set.h Jozsef Kadlecsik
2012-01-14 16:38 ` [PATCH 4/8] netfilter: ipset: Autoload set type modules safely Jozsef Kadlecsik
2012-01-14 16:38 ` [PATCH 5/8] netfilter: ipset: Dumping error triggered removing references twice Jozsef Kadlecsik
2012-01-14 16:38 ` [PATCH 6/8] netfilter: ipset: Log warning when a hash type of set gets full Jozsef Kadlecsik
2012-01-14 16:39 ` [PATCH 7/8] netfilter: ipset: Exceptions support added to hash:*net* types Jozsef Kadlecsik
2012-01-14 16:39 ` [PATCH 8/8] netfilter: ipset: hash:net,iface timeout bug fixed Jozsef Kadlecsik
2012-01-16 12:45 ` [PATCH 0/8] ipset patches Pablo Neira Ayuso
2012-01-16 15:52   ` Jozsef Kadlecsik
2012-01-16 23:08     ` Pablo Neira Ayuso [this message]
2012-01-16 23:16   ` Pablo Neira Ayuso
2012-01-17  8:18     ` Jozsef Kadlecsik
2012-01-17  9:46       ` Pablo Neira Ayuso

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=20120116230834.GA18052@1984 \
    --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).