public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: Mauro Carvalho Chehab <mchehab@brturbo.com.br>,
	Linus Torvalds <torvalds@osdl.org>,
	Ricardo Cerqueira <v4l@cerqueira.org>,
	linux-kernel@vger.kernel.org, video4linux-list@redhat.com
Subject: Re: Recursive dependency for SAA7134 in 2.6.15-rc7
Date: Thu, 5 Jan 2006 05:15:03 +0100	[thread overview]
Message-ID: <200601050515.07205.zippel@linux-m68k.org> (raw)
In-Reply-To: <20051231193956.4271e2f0.khali@linux-fr.org>

Hi,

On Saturday 31 December 2005 19:39, Jean Delvare wrote:

> So I believe that "choice" is an interesting Kconfig feature when used
> with boolean options, but with modules I am not convinced, especially
> when these modules have different dependencies.

Well, I'm always open to suggestions (or even better patches) to improve 
tristate choices. Such interdependent options have to be done via a choice 
group, so they are handled correctly handled by kconfig, otherwise you have 
to live with the current compromise. OTOH how they are mapped to the user 
interface is easily changeable.

bye, Roman

  reply	other threads:[~2006-01-05  4:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-27 20:53 Recursive dependency for SAA7134 in 2.6.15-rc7 Jean Delvare
2005-12-27 23:40 ` Mauro Carvalho Chehab
2005-12-28 20:02   ` Jean Delvare
2005-12-28 20:10     ` Mauro Carvalho Chehab
2005-12-29 20:00     ` Roman Zippel
2005-12-29 20:13       ` Jean Delvare
2005-12-29 20:19         ` Roman Zippel
2005-12-29 21:07           ` Jean Delvare
2005-12-30 10:01             ` Mauro Carvalho Chehab
2005-12-30 11:06               ` Jean Delvare
2005-12-30 13:39                 ` Mauro Carvalho Chehab
2005-12-31 18:39                   ` Jean Delvare
2006-01-05  4:15                     ` Roman Zippel [this message]
2006-01-05  8:28                       ` Jean Delvare
2005-12-29  3:20 ` Roman Zippel

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=200601050515.07205.zippel@linux-m68k.org \
    --to=zippel@linux-m68k.org \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@brturbo.com.br \
    --cc=torvalds@osdl.org \
    --cc=v4l@cerqueira.org \
    --cc=video4linux-list@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