linux-kernel - Re: linux-next: build warnings after merge of the kbuild-current tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4CAC59D4.5010505@suse.cz>
Date:	Wed, 06 Oct 2010 13:13:24 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Arnaud Lacombe <lacombar@...il.com>,
	Catalin Marinas <catalin.marinas@....com>
Subject: Re: linux-next: build warnings after merge of the kbuild-current
 tree

On 6.10.2010 02:44, Stephen Rothwell wrote:
> Hi Michal,
> 
> After merging the kbuild-current tree, today's (and yesterday's)
> linux-next build (x86_64 allmodconfig and other builds as well) produced
> these warnings:
> 
> warning: [...] selects I2C_ALGOBIT which has unmet direct dependencies (I2C && !I2C_HELPER_AUTO)
> [...]
> warning: [...] selects VIDEO_TVAUDIO which has unmet direct dependencies (MEDIA_SUPPORT && VIDEO_CAPTURE_DRIVERS && !VIDEO_HELPER_CHIPS_AUTO && VIDEO_V4L2 && I2C)
> 
> After reverting commit ff5ff6060bf880aac233e68dd666cbe9e39ec620
> ("kconfig: delay symbol direct dependency initialization") it produces no
> such warnings.

I'm aware of them. I'm talking with Jean Delvare about fixing the I2C
warnings, see http://lkml.org/lkml/2010/10/5/83. The drivers/media/video
warnings will need the same care. I don't know if we manage to fix these
in time, so maybe the kconfig fix will have to way for 2.6.36.1.

Michal

--
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/