public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kconfig Q: expressing a modularity dependency
Date: Sun, 23 Aug 2009 18:52:05 +0200	[thread overview]
Message-ID: <4A9173B5.10603@imap.cc> (raw)
In-Reply-To: <20090814163250.GD1626@ucw.cz>

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

Pavel Machek schrieb:

>> So I'll just put a notice in the help text then, warning people
>> not to set CONFIG_ISDN_DRV_GIGASET=y if their ISDN subsystem
>> is built as a module. If anybody has a better idea I'll be
>> glad to hear it.
> 
> That will break randconfig testing, AFAICT.

I don't think so. Ignoring the warning will not result in a build
failure, just in reduced functionality, and AFAIK that isn't an
issue in randconfig testing.

> AFAIK Kconfig supports if statement just fine, so can you just
> 
> if something
> 	bool GIGASET
> else
> 	tristate GIGASET

Interesting idea. I'll try that. It'll probably not make it into my
submission for 2.6.32 anymore, but perhaps it can be retrofitted
later.

Thanks,
Tilman

-- 
Tilman Schmidt                    E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

      reply	other threads:[~2009-08-23 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 14:01 Kconfig Q: expressing a modularity dependency Tilman Schmidt
2009-08-13 17:09 ` Tilman Schmidt
2009-08-14 16:32   ` Pavel Machek
2009-08-23 16:52     ` Tilman Schmidt [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=4A9173B5.10603@imap.cc \
    --to=tilman@imap.cc \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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