public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@linuxtv.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [build bug, 2.6.24-rc1] CONFIG_VIDEO_DEV=m & CONFIG_VIDEO_SAA7146_VV=y
Date: Mon, 29 Oct 2007 13:35:33 +0100	[thread overview]
Message-ID: <20071029123533.GA17331@linuxtv.org> (raw)
In-Reply-To: <20071029112303.GA18994@elte.hu>

On Mon, Oct 29, 2007, Ingo Molnar wrote:
> * Randy Dunlap <randy.dunlap@oracle.com> wrote:
> 
> > > config VIDEO_SAA7146_VV
> > > 	tristate
> > > 	depends on VIDEO_DEV = y || VIDEO_DEV = VIDEO_SAA7146_VV
> > > 	select VIDEOBUF_DMA_SG
> > > 	select VIDEO_SAA7146
> > > 
> > > (untested)
> > 
> > Nope, won't work.  I tried that last night.  VIDEO_DEV_SAA7146_VV
> > has too many "select"s involved, but select doesn't follow the dependency
> > chains.  IOW, as written in Documentation/kbuild/kconfig-language.txt:
> > 
> > 	select is evil.... select will by brute force set a symbol
> > 	equal to 'y' without visiting the dependencies. So abusing
> > 	select you are able to select a symbol FOO even if FOO depends
> > 	on BAR that is not set.
> 
> so ... what should we do? Remove those ~7 select VIDEO_SAA7146_VV lines 
> and replace them with depends on VIDEO_SAA7146_VV ?

Hm, the idea is that the SAA7146 driver is like a library,
and the V4L or DVB card drivers select the library functions
they need (base driver or common V4L helper functions).
The user shouldn't have to worry about those details.

But yeah, if it's not possible to do that with kbuild then
it's probably best to s/select/depends on/ for VIDEO_SAA7146_VV
and provide a meaningful help text for VIDEO_SAA7146_VV.


Johannes

  reply	other threads:[~2007-10-29 12:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26  7:37 [build bug, 2.6.24-rc1] CONFIG_VIDEO_DEV=m & CONFIG_VIDEO_SAA7146_VV=y Ingo Molnar
2007-10-27 21:30 ` Johannes Stezenbach
2007-10-27 23:39   ` Randy Dunlap
2007-10-29 11:23     ` Ingo Molnar
2007-10-29 12:35       ` Johannes Stezenbach [this message]
2007-10-29 18:19         ` Randy Dunlap
2007-10-29 15:16       ` Mauro Carvalho Chehab
2007-10-31 12:11 ` Trent Piepho
2007-11-01  9:01   ` Ingo Molnar
2007-11-01  9:40     ` Mauro Carvalho Chehab
2007-11-01 10:34     ` Trent Piepho
2007-11-01 10:57       ` Ingo Molnar
2007-11-02  0:12         ` Trent Piepho
2007-11-02 15:28           ` Ingo Molnar
2007-11-02 21:12             ` Mauro Carvalho Chehab

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=20071029123533.GA17331@linuxtv.org \
    --to=js@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=mingo@elte.hu \
    --cc=randy.dunlap@oracle.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