From: Al Viro <viro@ftp.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 13/13] fix ps3fb glue allowing a modular build
Date: Wed, 14 Mar 2007 17:59:36 +0000 [thread overview]
Message-ID: <20070314175936.GM4095@ftp.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0703141016060.9690@woody.linux-foundation.org>
On Wed, Mar 14, 2007 at 10:30:31AM -0700, Linus Torvalds wrote:
> > Nope. How can kconfig distinguish that from a boolean option in modular
> > driver? bool *can* depend on tristate and be selected when tristate is
> > set to m.
>
> Btw, this is one of those things that easily causes problems.
>
> In many ways it would be nice if we had two different kinds of "bool": one
> where "m" in the dependency chain means "y" is ok, and one where "m" means
> "n".
*nod*
> Maybe not "bool" vs "mbool", but it might be nice to have
>
> bool FB_PS3
> depends strictly on FB
>
> ie a "depends strictly" refuses to upgrade a bool dependency from "m" to
> "y", while a regular depends allows it.
>
> Or something.. The "depends strictly on X" thing would really be just a
> mental shorthand for "depends on (X)=y" (it's actually longer to type, but
> I think it's a bit more intuitive, thus "mental shortcut").
There's a fun side question, though: what should allmodconfig do? FB=m,
FB_PS3=n? Or FB=y, FB_PS3=y?
next prev parent reply other threads:[~2007-03-14 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 9:17 [PATCH 13/13] fix ps3fb glue allowing a modular build Al Viro
2007-03-14 9:50 ` Geert Uytterhoeven
2007-03-14 16:02 ` Al Viro
2007-03-14 16:17 ` Geert Uytterhoeven
2007-03-14 17:07 ` Al Viro
2007-03-14 17:23 ` Geert Uytterhoeven
2007-03-14 17:30 ` Linus Torvalds
2007-03-14 17:45 ` Geert Uytterhoeven
2007-03-14 17:59 ` Al Viro [this message]
2007-03-14 18:09 ` Geert Uytterhoeven
2007-03-14 18:25 ` Al Viro
2007-03-15 1:17 ` Antonino A. Daplas
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=20070314175936.GM4095@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).