From: Oliver <oliver@8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpa>
To: netfilter-devel@vger.kernel.org
Subject: [PATCH v2 0/2] ipset: rework extension handling to be more manageable.
Date: Sun, 1 Sep 2013 21:58:40 +0200 [thread overview]
Message-ID: <1378065522-65492-1-git-send-email-oliver@8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpa> (raw)
From: Oliver Smith <oliver@8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpa>
Earlier today I sent a patch that cleaned up the hash extension, not noticing
that the bitmap family is in a similar state.
This series cleans up the code for both the hash and bitmap families. Patch 1 is
identical to the one I sent earlier today but has a different commit message that
specifically mentions that it applies to the hash family.
Oliver Smith (2):
netfilter: ipset: rework hash ext. handling to be more manageable.
netfilter: ipset: rework bitmap ext. handling to be more manageable.
kernel/include/uapi/linux/netfilter/ipset/ip_set.h | 8 +-
kernel/net/netfilter/ipset/ip_set_bitmap_gen.h | 55 ++++++++++
kernel/net/netfilter/ipset/ip_set_bitmap_ip.c | 68 ++----------
kernel/net/netfilter/ipset/ip_set_bitmap_ipmac.c | 63 ++---------
kernel/net/netfilter/ipset/ip_set_bitmap_port.c | 57 +---------
kernel/net/netfilter/ipset/ip_set_hash_gen.h | 121 ++++++++-------------
6 files changed, 129 insertions(+), 243 deletions(-)
--
1.8.3.2
next reply other threads:[~2013-09-01 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 19:58 Oliver [this message]
2013-09-01 19:58 ` [PATCH v2 1/2] netfilter: ipset: rework hash ext. handling to be more manageable Oliver
2013-09-01 19:58 ` [PATCH v2 2/2] netfilter: ipset: rework bitmap " Oliver
2013-09-02 20:04 ` [PATCH v2 0/2] ipset: rework extension " Jozsef Kadlecsik
2013-09-03 10:49 ` Oliver
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=1378065522-65492-1-git-send-email-oliver@8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpa \
--to=oliver@8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpa \
--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).