From: Michal Marek <mmarek@suse.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Arnaud Lacombe <lacombar@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
brueckner@linux.vnet.ibm.com, mchehab@redhat.com,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: visibility changes (was: Re: [GIT] kbuild and kconfig fixes for 2.6.37-rc5)
Date: Thu, 16 Dec 2010 22:43:47 +0100 [thread overview]
Message-ID: <4D0A8813.7060909@suse.cz> (raw)
In-Reply-To: <AANLkTin8Xf9SPcHrBPRPg+cnbWO94CwB4u6KQ2it1+Y9@mail.gmail.com>
On 7.12.2010 21:45, Geert Uytterhoeven wrote:
> On Tue, Dec 7, 2010 at 21:40, Arnaud Lacombe<lacombar@gmail.com> wrote:
>> On Tue, Dec 7, 2010 at 3:31 PM, Geert Uytterhoeven<geert@linux-m68k.org> wrote:
>>> On Tue, Dec 7, 2010 at 20:51, Arnaud Lacombe<lacombar@gmail.com> wrote:
>>>> On Tue, Dec 7, 2010 at 2:07 PM, Geert Uytterhoeven<geert@linux-m68k.org> wrote:
>>>>> BTW, I got confused:
>>>>> - make allmodconfig causes e.g.:
>>>>> CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
>>>>> CONFIG_VIDEO_TVAUDIO=m
>>>>> => good
>>>>> - make oldconfig for my config with almost everything selected,
>>>>> except for stuff I know that breaks:
>>>>> CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
>>>>> # CONFIG_VIDEO_TVAUDIO is not set
>>>>> and no way to manually set CONFIG_VIDEO_TVAUDIO=y?
>>>>> => bad!
>>>> that's difficult to judge without your old configuration.
>>>> VIDEO_TVAUDIO is only selected by VIDEO_BT848 which you don't give
>>>> information about.
>>>
>>> I don't have PCI, so I cannot enable VIDEO_BT848.
>>>
>> so why do you expect VIDEO_TVAUDIO to be enabled ?
>
> I don't expect it to be enabled, I expected to be able to enable it.
> Allmodconfig
> does enable it.
Actually allmodconfig should not enable it, as it did not so before the
patch. See Jan's fix at https://patchwork.kernel.org/patch/393302/
Michal
prev parent reply other threads:[~2010-12-16 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 19:07 visibility changes (was: Re: [GIT] kbuild and kconfig fixes for 2.6.37-rc5) Geert Uytterhoeven
2010-12-07 19:51 ` Arnaud Lacombe
2010-12-07 20:31 ` Geert Uytterhoeven
2010-12-07 20:40 ` Arnaud Lacombe
2010-12-07 20:45 ` Geert Uytterhoeven
2010-12-07 22:36 ` Mauro Carvalho Chehab
2010-12-08 8:57 ` Geert Uytterhoeven
2010-12-16 21:43 ` Michal Marek [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=4D0A8813.7060909@suse.cz \
--to=mmarek@suse.cz \
--cc=brueckner@linux.vnet.ibm.com \
--cc=geert@linux-m68k.org \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--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