From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: ipset maximal/minimal revision conflict
Date: Tue, 26 Apr 2011 20:25:37 +0100 [thread overview]
Message-ID: <4DB71C31.6030106@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1104262007050.2868@blackhole.kfki.hu>
> You can copy over the files (header files too) from the ipset package to
> the kernel tree.
>
Actually, what I did was to create 1 mega patch with 1) the difference
between .39-rc4 and .35-88 (the latest stable kernel released by Fedora)
as far as the ipset kernel modules are concerned; 2) all
menuconfig-related ipset settings (so that when I run make menuconfig I
could select the ipset settings properly); and 3) the difference between
.39-rc4 (git as of 24 April) and ipset 6.4 (the kernel part).
Applied it successfully to the kernel source tree and I am now building
it (.35.12-88). If/When it finishes I'll install it on my test harness
here and will see how it goes. I briefly looked at the differences
between the 6.4 release and the latest kernel modules I've had from that
git and they are quite extensive indeed.
One thing I also noticed - in the kernel part of v6.4 you have
"-DCONFIG_IP_SETMAX" extra CFLAGS defined, but that seems to be missing
from the git kernel tree - is that on purpose or is this new to be added
later on?
By the time I typed this the kernel build has completed successfully.
Installation and testing follows...
prev parent reply other threads:[~2011-04-26 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 11:16 ipset maximal/minimal revision conflict Mr Dash Four
2011-04-26 14:05 ` Jozsef Kadlecsik
2011-04-26 15:06 ` Mr Dash Four
2011-04-26 18:11 ` Jozsef Kadlecsik
2011-04-26 19:25 ` Mr Dash Four [this message]
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=4DB71C31.6030106@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=kadlec@blackhole.kfki.hu \
--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 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.