From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 0/6] ipset updates for nf-next
Date: Thu, 2 May 2013 12:07:59 +0200 [thread overview]
Message-ID: <20130502100759.GB3432@localhost> (raw)
In-Reply-To: <1367487442-3571-1-git-send-email-kadlec@blackhole.kfki.hu>
Hi Jozsef,
On Thu, May 02, 2013 at 11:37:16AM +0200, Jozsef Kadlecsik wrote:
> Hi Pablo,
>
> Here follows the ipset related updates for nf-next: sparse warning fixes,
> cleanups and small corrections. Please consider applying them.
Thanks for the patches, but the merge window is now closed.
I can only take bugfixes until 3.10-rc1 is released. They will have to
wait until then.
Regards.
next prev parent reply other threads:[~2013-05-02 10:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 9:37 [PATCH 0/6] ipset updates for nf-next Jozsef Kadlecsik
2013-05-02 9:37 ` [PATCH 1/6] netfilter: ipset: Don't call ip_nest_end needlessly in the error path Jozsef Kadlecsik
2013-05-02 9:37 ` [PATCH 2/6] netfilter: ipset: Sparse warning about shadowed variable fixed Jozsef Kadlecsik
2013-05-02 9:37 ` [PATCH 3/6] netfilter: ipset: Fix sparse warnings due to missing rcu annotations Jozsef Kadlecsik
2013-05-02 10:08 ` Pablo Neira Ayuso
2013-05-02 9:37 ` [PATCH 4/6] netfilter: ipset: Rename simple macro names to avoid namespace issues Jozsef Kadlecsik
2013-05-02 9:37 ` [PATCH 5/6] netfilter: ipset: Fix "may be used uninitialized" warnings Jozsef Kadlecsik
2013-05-02 10:09 ` Pablo Neira Ayuso
2013-05-02 9:37 ` [PATCH 6/6] netfilter: ipset: Use fix sized type for timeout in the extension part Jozsef Kadlecsik
2013-05-02 10:07 ` Pablo Neira Ayuso [this message]
2013-05-02 10:14 ` [PATCH 0/6] ipset updates for nf-next Jozsef Kadlecsik
2013-05-02 10:29 ` 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=20130502100759.GB3432@localhost \
--to=pablo@netfilter.org \
--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).