[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikVM=zakYF7uhX1mYHy9QUVL6dmEPNsmV7=oyuh@mail.gmail.com>
Date: Tue, 7 Dec 2010 20:07:09 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Michal Marek <mmarek@...e.cz>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
brueckner@...ux.vnet.ibm.com, lacombar@...il.com,
mchehab@...hat.com, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: visibility changes (was: Re: [GIT] kbuild and kconfig fixes for 2.6.37-rc5)
On Sat, Dec 4, 2010 at 14:57, Michal Marek <mmarek@...e.cz> wrote:
> please pull these kbuild/kconfig fixes for the next -rc. The largest
> part are fixes for the annoying kconfig warnings, contributed by Arnaud
> Lacombe and Mauro Carvalho Chehab. The solution adds a new 'visible if'
> keyword to the Kconfig language, so it's not exactly something that one
> would expect in the rc phase, but the kconfig change is not huge (the
> large diff is due to generated files) and it is deployed only in those
> five Kconfig files that had the warnings and were hard to fix by other
> means. The second part is a forgotten patch by Hendrik Brueckner to
> usr/initramfs, that fixes build for Blackfin and h8300.
> Arnaud Lacombe (5):
> kconfig: add an option to determine a menu's visibility
Hmm, this changeset also went in through the v4l tree?
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!
Is this intentional?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists