From: Harald Welte <laforge@netfilter.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Linux Netdev List <netdev@vger.kernel.org>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [HELP] netfilter Kconfig dependency nightmare
Date: Sat, 17 Sep 2005 17:29:31 +0200 [thread overview]
Message-ID: <20050917152931.GA8413@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0509171407460.3743@scrub.home>
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
On Sat, Sep 17, 2005 at 02:18:28PM +0200, Roman Zippel wrote:
> Since IP_NF_CONNTRACK_NETLINK is the one creating the dependency,
> something like this should work:
yes, I agree. Looking at the behaviour of "menuconfig", I think your
suggestion solves the problem. I didn't try to compile all the
combinations, though.
I'll submit a patch via DaveM soon.
--
- Harald Welte <laforge@netfilter.org> http://netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-17 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050916021451.3012196c.akpm@osdl.org>
[not found] ` <20050916191959.GN8413@sunbeam.de.gnumonks.org>
[not found] ` <39e6f6c705091617514457eded@mail.gmail.com>
[not found] ` <20050917012315.GA29841@mandriva.com>
2005-09-17 8:07 ` Harald Welte
2005-09-17 11:08 ` Roman Zippel
2005-09-17 11:29 ` Harald Welte
2005-09-17 12:18 ` Roman Zippel
2005-09-17 15:29 ` Harald Welte [this message]
2005-09-17 15:32 ` Arnaldo Carvalho de Melo
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=20050917152931.GA8413@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®