From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
jkosina@suse.cz, "David S. Miller" <davem@davemloft.net>
Subject: resend your pending patches, please
Date: Tue, 27 Oct 2009 15:02:30 +0100 [thread overview]
Message-ID: <4AE6FD76.40705@netfilter.org> (raw)
Hi all,
While Patrick is recovering, I'll temporarily do the netfilter/iptables
kernel-space maintainance. While spinning on the mailing list, I have
found two pending patches that can be qualified as bugfixes:
[PATCH] netfilter: remove CONFIG_NF_CT_ACCT from Jiri Kosina
[PATCH] netfilter: nf_nat: fix NAT issue in 2.6.30.4+
If I'm missing any other patch, please let me know.
Once this bugfix round is done, I'll look at net-next-2.6 patches. I
have seen one patchset from Jan Engelhardt so far.
Thank you!
next reply other threads:[~2009-10-27 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 14:02 Pablo Neira Ayuso [this message]
2009-10-27 14:03 ` resend your pending patches, please Pablo Neira Ayuso
2009-10-28 15:44 ` Patrick McHardy
2009-10-29 10:31 ` Pablo Neira Ayuso
2009-10-29 16:02 ` Patrick McHardy
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=4AE6FD76.40705@netfilter.org \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=jkosina@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.