From: pablo@netfilter.org
To: netfilter-devel@vger.kernel.org
Cc: jengelh@medozas.de, kaber@trash.net, kadlec@blackhole.kfki.hu
Subject: [PATCH] [RFC] ip_queue removal
Date: Tue, 17 Jan 2012 00:12:02 +0100 [thread overview]
Message-ID: <1326755523-2762-1-git-send-email-pablo@netfilter.org> (raw)
From: Pablo Neira Ayuso <pablo@netfilter.org>
Hi,
I'm thinking about pushing the following patch to net-next once becomes
active.
Does anyone have any compelling reason to keep ip_queue still in the
tree?
Pablo Neira Ayuso (1):
netfilter: remove ip_queue support
Documentation/ABI/removed/ip_queue | 9 +
include/linux/netfilter_ipv4/ip_queue.h | 72 ----
include/linux/netlink.h | 2 +-
net/ipv4/netfilter/Makefile | 3 -
net/ipv4/netfilter/ip_queue.c | 639 -------------------------------
5 files changed, 10 insertions(+), 715 deletions(-)
create mode 100644 Documentation/ABI/removed/ip_queue
delete mode 100644 include/linux/netfilter_ipv4/ip_queue.h
delete mode 100644 net/ipv4/netfilter/ip_queue.c
--
1.7.7.3
next reply other threads:[~2012-01-16 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 23:12 pablo [this message]
2012-01-16 23:12 ` [PATCH] netfilter: remove ip_queue support pablo
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=1326755523-2762-1-git-send-email-pablo@netfilter.org \
--to=pablo@netfilter.org \
--cc=jengelh@medozas.de \
--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).