cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [GFS2] Fix Kconfig [2/2]
Date: Mon, 18 Dec 2006 11:10:40 +0000	[thread overview]
Message-ID: <1166440240.3752.1276.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0612181149420.22591@yvahk01.tjqt.qr>

Hi,

On Mon, 2006-12-18 at 11:50 +0100, Jan Engelhardt wrote:
> On Dec 18 2006 09:57, Steven Whitehouse wrote:
> > config GFS2_FS_LOCKING_DLM
> > 	tristate "GFS2 DLM locking module"
> >-	depends on GFS2_FS
> >+	depends on GFS2_FS && NET && INET && (IPV6 || IPV6=n)
> 
> What is this supposed to do? IPV6 || IPV6=n is a tautology AFAICS.
> 
> 
> 	-`J'

It looks odd, I'll grant you, but see the thread entitled "Re: [PATCH]
Remove logically superfluous comparisons from Kconfig files." and the
answer that Russell King has just given on the same subject where he
says:

>config FOO
>        tristate 'foo'
>        depends on BAR || BAR=n
>
>is not superfluous.  The allowed states for FOO with the above
>construct are (assuming modules are enabled):
>
>        BAR     FOO
>        Y       Y,M,N
>        M       M,N
>        N       Y,M,N

which hopefully explains it a bit better,

Steve.




      parent reply	other threads:[~2006-12-18 11:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18  9:54 [Cluster-devel] [DLM] Fix compile warning [1/2] Steven Whitehouse
2006-12-18  9:57 ` [Cluster-devel] [GFS2] Fix Kconfig [2/2] Steven Whitehouse
2006-12-18 10:01   ` [Cluster-devel] [GFS2 & DLM] Pull request Steven Whitehouse
2006-12-18 10:50   ` [Cluster-devel] Re: [GFS2] Fix Kconfig [2/2] Jan Engelhardt
2006-12-18 11:09     ` Robert P. J. Day
2006-12-18 11:10     ` Steven Whitehouse [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=1166440240.3752.1276.camel@quoit.chygwyn.com \
    --to=swhiteho@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).