public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] DLM must depend on IPV6 || IPV6=n
Date: Tue, 9 Aug 2005 17:58:27 +0200	[thread overview]
Message-ID: <20050809155827.GD17488@lug-owl.de> (raw)
In-Reply-To: <20050809155001.GZ4006@stusta.de>

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

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?

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-09 15:58 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 [this message]
2005-08-12  0:50   ` Adrian Bunk
  -- 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=20050809155827.GD17488@lug-owl.de \
    --to=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