From: "David S. Miller" <davem@davemloft.net>
To: laforge@netfilter.org
Cc: kaber@trash.net, akpm@osdl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix NFQUEUE Kconfig dependency
Date: Sat, 24 Sep 2005 16:52:18 -0700 (PDT) [thread overview]
Message-ID: <20050924.165218.131424970.davem@davemloft.net> (raw)
In-Reply-To: <20050923150631.GH731@sunbeam.de.gnumonks.org>
From: Harald Welte <laforge@netfilter.org>
Date: Fri, 23 Sep 2005 17:06:31 +0200
> [NETFILTER]: Fix ip[6]t_NFQUEUE Kconfig dependency
>
> We have to introduce a separate Kconfig menu entry for the NFQUEUE targets.
> They cannot "just" depend on nfnetlink_queue, since nfnetlink_queue could
> be linked into the kernel, whereas iptables can be a module.
>
> Signed-off-by: Harald Welte <laforge@netfilter.org>
Applied, thanks Harald.
prev parent reply other threads:[~2005-09-24 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050923014412.26695cc4.akpm@osdl.org>
[not found] ` <433412A6.2090904@trash.net>
2005-09-23 15:06 ` [PATCH] fix NFQUEUE Kconfig dependency (was Re: Fw: Kernel 2.6.14-rc2 compile error) Harald Welte
2005-09-24 23:52 ` David S. Miller [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=20050924.165218.131424970.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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