From: Chris Clayton <chris2553@googlemail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Warnings from latest -git
Date: Tue, 2 Nov 2010 19:09:02 +0000 [thread overview]
Message-ID: <201011021909.02175.chris2553@googlemail.com> (raw)
In-Reply-To: <4CD00423.4060309@redhat.com>
Thanks for the reply, Mauro.
On Tuesday 02 November 2010, Mauro Carvalho Chehab wrote:
> Em 30-10-2010 04:17, Chris Clayton escreveu:
> > Hi,
> >
> > Please cc me on any reply as I'm not subscribed.
> >
> > Building v2.6.36-9452-g2d10d87 pulled this morning, I get:
> >
> > warning: (DVB_USB_DIB0700 && MEDIA_SUPPORT && DVB_CAPTURE_DRIVERS &&
> > DVB_CORE && DVB_USB && !DVB_FE_CUSTOMISE) selects DVB_DIB8000 which has
> > unmet direct dependencies (MEDIA_SUPPORT && DVB_CAPTURE_DRIVERS &&
> > DVB_FE_CUSTOMISE && DVB_CORE && I2C)
>
> It certainly requires further investigation. From your config file, we
> have, for dib0700:
>
> CONFIG_DVB_USB_DIB0700=m
> CONFIG_MEDIA_SUPPORT=m
> CONFIG_DVB_CAPTURE_DRIVERS=y
> CONFIG_DVB_CORE=m
> CONFIG_DVB_USB=m
> # CONFIG_DVB_FE_CUSTOMISE is not set
>
> And, for dib8000:
>
> CONFIG_MEDIA_SUPPORT=m
> CONFIG_DVB_CAPTURE_DRIVERS=y
> # CONFIG_DVB_FE_CUSTOMISE is not set
> CONFIG_DVB_CORE=m
> CONFIG_I2C=y
>
> Both dib0700 and dib8000 were marked as m:
>
> CONFIG_DVB_DIB8000=m
> CONFIG_DVB_USB_DIB0700=m
>
> So, in this specific example, it actually worked, but we need to find a fix
> for this bug.
>
I may be wrong, but I don't see why DVB_FE_CUSTOMISE is a dependency in these
two cases. When it is not set, all the FE drivers are built. When it is set,
the user selects, which drivers are to be built, but what I think the select
statements are doing is select drivers without which other selections the user
has made make little sense. If that's correct, the DVB_FE_CUSTOMISE can simply
be removed as dependencies.
Let me know if that makes sense and, if it does, I'll bake a patch.
I've now customised anyway, so teh warnings have gone away, but can soon revert
that to test a fix.
Thanks
Chris
> Cheers,
> Mauro
--
The more I see, the more I know. The more I know, the less I understand.
Changing Man - Paul Weller
prev parent reply other threads:[~2010-11-02 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 8:17 Warnings from latest -git Chris Clayton
2010-11-02 12:29 ` Mauro Carvalho Chehab
2010-11-02 19:09 ` Chris Clayton [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=201011021909.02175.chris2553@googlemail.com \
--to=chris2553@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).