mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Alistair John Strachan <alistair@devzero.co.uk>,
	Robin Holt <holt@sgi.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.26-rc1
Date: Wed, 07 May 2008 01:36:09 +0200	[thread overview]
Message-ID: <4820EB69.9090907@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080506193928.5acfc84d@gaivota>

Mauro Carvalho Chehab wrote:
> On Tue, 06 May 2008 22:47:20 +0200
> Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
>> Or another idea:
>>
>> Copy _all_ dependencies of drivers which can be selected by "...if 
    ^^^^
>> VIDEO_HELPER_CHIPS_AUTO" to VIDEO_HELPER_CHIPS_AUTO.
> 
> I actually did this for tuners, on this changeset (still not at mainstream):
> http://git.kernel.org/?p=linux/kernel/git/mchehab/v4l-dvb.git;a=commitdiff;h=d10b3c6817fb3fed8e6cd6d64d47c187a615c952

Yes...  Except that it is very dangerous to /move/ dependencies, as you 
are apparently doing in that patch.  When you use "select" somewhere, 
you should generally /copy/ dependencies.

Although something like

config VIRTUAL_META_OPTION
	depends on REAL_DEPENDENCY

config THE_REAL_THING
	depends on VIRTUAL_META_OPTION

does work if THE_REAL_THING actually depends on REAL_DEPENDENCY, it is 
safer if this dependency stays there, i.e.

config THE_REAL_THING
	depends on REAL_DEPENDECY

or

config THE_REAL_THING
	depends on REAL_DEPENDENCY && VIRTUAL_META_OPTION

or whatever, or equivalent constructs involving "if"..."endif".

(I presume that for example MEDIA_TUNER_TDA827X does indeed have a build 
dependency on DVB_CORE && I2C.)

Or in other words:

Since MEDIA_TUNER selects a bunch of options which itself have build 
dependencies, you /must/ duplicate all of their dependencies to 
MEDIA_TUNER.  Well, actually you don't use plain "select", you use 
"select ... if !MEDIA_TUNER_CUSTOMIZE".  So if you can ensure by other 
means that those 2nd level dependencies are guaranteed to be fulfilled 
whenever MEDIA_TUNER_CUSTOMIZE=n, then you don't need to duplicate the 
2nd level dependencies into MEDIA_TUNER.

That's the same what I meant in my comment on VIDEO_HELPER_CHIPS_AUTO:

Those options which "select" video decoders generally /must/ contain 
duplicates of the dependency statements of the decoders which they 
select.  Except, since you don't use plain "select" there but actually 
"select ... if VIDEO_HELPER_CHIPS_AUTO", you can alternatively put the 
duplicates of the dependency statements to VIDEO_HELPER_CHIPS_AUTO.
-- 
Stefan Richter
-=====-==--- -=-= --===
http://arcgraph.de/sr/

  reply	other threads:[~2008-05-06 23:36 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8287f540805041818g534c4e02qaadb0e749c5f3439@mail.gmail.com>
2008-05-03 19:38 ` Linus Torvalds
2008-05-03 21:47   ` Alistair John Strachan
2008-05-03 21:53     ` Alistair John Strachan
2008-05-04 12:30       ` Robin Holt
2008-05-04 13:56         ` Alistair John Strachan
2008-05-04 16:09           ` Robin Holt
2008-05-04 16:33             ` Alistair John Strachan
2008-05-05 21:04             ` Mauro Carvalho Chehab
2008-05-06  8:02               ` Alistair John Strachan
2008-05-06 10:31                 ` Mauro Carvalho Chehab
2008-05-06 14:34                   ` Stefan Richter
2008-05-06 14:54                     ` Stefan Richter
2008-05-06 19:13                     ` Mauro Carvalho Chehab
2008-05-06 19:44                       ` Stefan Richter
2008-05-06 20:06                         ` Mauro Carvalho Chehab
2008-05-06 20:47                           ` Stefan Richter
2008-05-06 22:39                             ` Mauro Carvalho Chehab
2008-05-06 23:36                               ` Stefan Richter [this message]
2008-05-08 12:48                                 ` Mauro Carvalho Chehab
2008-05-08 14:11                                   ` Stefan Richter
2008-05-06 23:48                             ` Stefan Richter
2008-05-04  7:29   ` [patch] sysfs: build fix Ingo Molnar
2008-05-04 18:40   ` Linux 2.6.26-rc1 Jan Engelhardt
2008-05-05  5:39   ` Andreas Mohr
2008-05-05  7:30     ` Ingo Molnar
2008-05-05 20:14       ` Mauro Carvalho Chehab
2008-05-06 13:07         ` Ingo Molnar
2008-05-07  8:35           ` Ingo Molnar
2008-05-05 23:51       ` Stephen Rothwell
2008-05-05 23:55         ` David Miller
2008-05-06  0:16           ` Andrew Morton
2008-05-06  5:57             ` Stephen Rothwell
2008-05-06  0:21           ` Ingo Molnar
2008-05-06  5:35           ` Stephen Rothwell
2008-05-06  6:56             ` David Miller
2008-05-06  7:26               ` Stephen Rothwell
2008-05-06  0:17         ` Ingo Molnar
2008-05-06  5:48           ` Stephen Rothwell
2008-05-06  6:07   ` Scheduling problems ? [ Was: Linux 2.6.26-rc1 ] J.A. Magallón
2008-05-06 13:11     ` Ingo Molnar

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=4820EB69.9090907@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=alistair@devzero.co.uk \
    --cc=holt@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.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

Powered by JetHome