From: Adrian Bunk <bunk@stusta.de>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>, linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] DLM must depend on IPV6 || IPV6=n
Date: Fri, 12 Aug 2005 02:50:11 +0200 [thread overview]
Message-ID: <20050812005011.GU4006@stusta.de> (raw)
In-Reply-To: <20050809155827.GD17488@lug-owl.de>
On Tue, Aug 09, 2005 at 05:58:27PM +0200, Jan-Benedict Glaw wrote:
> On Tue, 2005-08-09 17:50:01 +0200, Adrian Bunk <bunk@stusta.de> wrote:
> > This patch fixes the following compile error with CONFIG_DLM=y and
> > CONFIG_IPV6=m:
>
> [...]
>
> > --- linux-2.6.13-rc3-mm3-modular/drivers/dlm/Kconfig.old 2005-07-30 14:07:12.000000000 +0200
> > +++ linux-2.6.13-rc3-mm3-modular/drivers/dlm/Kconfig 2005-07-30 14:07:41.000000000 +0200
> > @@ -3,6 +3,7 @@
> >
> > config DLM
> > tristate "Distributed Lock Manager (DLM)"
> > + depends on IPV6 || IPV6=n
> > select IP_SCTP
> > help
> > A general purpose distributed lock manager for kernel or userspace
>
> Why don't you allow modular builds of both? ...or aren't the IPv6
> symbols exported?
Modular builds of both are supported.
CONFIG_DLM=y and CONFIG_IPV6=m is the evil combination since
CONFIG_IP_SCTP=y and CONFIG_IPV6=m doesn't compile.
> MfG, JBG
cu
Adrian
BTW: Please don't strip people from replies.
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-08-12 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 15:50 [-mm patch] DLM must depend on IPV6 || IPV6=n Adrian Bunk
2005-08-09 15:58 ` Jan-Benedict Glaw
2005-08-12 0:50 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-30 14:12 Adrian Bunk
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=20050812005011.GU4006@stusta.de \
--to=bunk@stusta.de \
--cc=jbglaw@lug-owl.de \
--cc=linux-kernel@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