From: Michael Tokarev <mjt@tls.msk.ru>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [ANNOUNCE] ipset 6.2 released
Date: Wed, 30 Mar 2011 00:02:29 +0400 [thread overview]
Message-ID: <4D923AD5.6090907@msgid.tls.msk.ru> (raw)
In-Reply-To: <4D923687.6030003@msgid.tls.msk.ru>
29.03.2011 23:44, Michael Tokarev пишет:
> 29.03.2011 23:23, Jozsef Kadlecsik wrote:
>> On Tue, 29 Mar 2011, Michael Tokarev wrote:
>>
>>> ipset-6.2/kernel/net/netfilter/ipset/Kconfig file
>>> appears to be some net/netfilter/Kconfig file from
>>> linux source tree (from one directory level up),
>>> patched with NETFILTER_XT_SET. It gets included
>>> into itself recursively.
>>
>> Yes, you are right, I fixed it in the ipset git tree. Thanks!
>
> Actually I'm not sure at all this file is needed.
>
> With current Kbuild file, it builds everything as
> modules, the only CONFIG_FOO in use is IP_SET_MAX
> which can be specfied in the upper-level Kconfig
> (in net/netfilter/Kconfig).
Maybe something like this:
net/netfilter/ipset/Makefile:
ip_set-y := ip_set_core.o ip_set_getport.o pfxlen.o
obj-$(CONFIG_IP_SET) += ip_set.o
obj-$(CONFIG_IP_SET_BITMAP_IP) += ip_set_bitmap_ip.o
obj-$(CONFIG_IP_SET_BITMAP_IPMAC) += ip_set_bitmap_ipmac.o
obj-$(CONFIG_IP_SET_BITMAP_PORT) += ip_set_bitmap_port.o
obj-$(CONFIG_IP_SET_HASH_IP) += ip_set_hash_ip.o
obj-$(CONFIG_IP_SET_HASH_IPPORT) += ip_set_hash_ipport.o
obj-$(CONFIG_IP_SET_HASH_IPPORTIP) += ip_set_hash_ipportip.o
obj-$(CONFIG_IP_SET_HASH_NET) += ip_set_hash_net.o
obj-$(CONFIG_IP_SET_HASH_IPPORTNET) += ip_set_hash_ipportnet.o
obj-$(CONFIG_IP_SET_HASH_NETPORT) += ip_set_hash_netport.o
obj-$(CONFIG_IP_SET_LIST_SET) += ip_set_list_set.o
---- cut ----
net/netfilter/Kbuild.ipset:
obj-$(CONFIG_XT_SET) += xt_set.o
obj-$(CONFIG_IP_SET) += ipset/
--- cut ---
(this should go to net/netfilter/Makefile in the upstream
kernel sources; ditto for the Kconfig bits).
This is all, obviously, about integration into mainline
kernel.
Do you plan to include the whole thing into mainline kernel?
Thanks!
/mjt
next prev parent reply other threads:[~2011-03-29 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 19:30 [ANNOUNCE] ipset 6.2 released Jozsef Kadlecsik
2011-03-29 14:08 ` Michael Tokarev
2011-03-29 19:23 ` Jozsef Kadlecsik
2011-03-29 19:44 ` Michael Tokarev
2011-03-29 20:02 ` Michael Tokarev [this message]
2011-03-29 20:06 ` Jozsef Kadlecsik
2011-03-29 20:23 ` Jozsef Kadlecsik
2011-03-29 20:02 ` Jozsef Kadlecsik
2011-03-29 20:18 ` Michael Tokarev
2011-03-29 20:19 ` Michael Tokarev
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=4D923AD5.6090907@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@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).