From: Michal Marek <mmarek@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnaud Lacombe <lacombar@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: linux-next: build warnings after merge of the kbuild-current tree
Date: Wed, 06 Oct 2010 13:13:24 +0200 [thread overview]
Message-ID: <4CAC59D4.5010505@suse.cz> (raw)
In-Reply-To: <20101006114433.4fbe86ef.sfr@canb.auug.org.au>
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
next prev parent reply other threads:[~2010-10-06 11:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 0:44 linux-next: build warnings after merge of the kbuild-current tree Stephen Rothwell
2010-10-06 11:13 ` Michal Marek [this message]
2010-10-06 11:42 ` Catalin Marinas
2010-10-08 14:51 ` Michal Marek
2010-10-08 15:03 ` Américo Wang
2010-10-08 15:05 ` Michal Marek
2010-10-09 21:45 ` [PATCH] kconfig: Temporarily disable dependency warnings Michal Marek
2010-10-11 15:23 ` Catalin Marinas
2010-10-11 21:46 ` Michal Marek
2010-10-11 21:59 ` Randy Dunlap
2010-10-12 13:19 ` [PATCH] Revert "kconfig: Temporarily disable dependency warnings" Michal Marek
2010-10-29 0:37 ` Stephen Rothwell
2010-11-22 0:48 ` Stephen Rothwell
2010-11-22 1:44 ` Randy Dunlap
2010-11-22 1:58 ` Arnaud Lacombe
2010-11-22 1:58 ` Arnaud Lacombe
2010-11-22 2:09 ` Randy Dunlap
2010-11-22 2:09 ` Randy Dunlap
2010-11-22 2:17 ` Arnaud Lacombe
2010-11-22 2:57 ` Stephen Rothwell
2010-11-22 13:26 ` Mauro Carvalho Chehab
2010-11-25 17:16 ` Arnaud Lacombe
2010-11-25 17:16 ` Arnaud Lacombe
2010-11-25 17:43 ` Catalin Marinas
2010-11-25 17:43 ` Catalin Marinas
2010-11-25 18:09 ` Arnaud Lacombe
2010-11-25 18:09 ` Arnaud Lacombe
2010-11-26 12:33 ` Catalin Marinas
2010-11-26 12:33 ` Catalin Marinas
2010-11-26 13:33 ` Michal Marek
2010-11-26 14:50 ` Catalin Marinas
2010-11-25 19:26 ` Mauro Carvalho Chehab
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=4CAC59D4.5010505@suse.cz \
--to=mmarek@suse.cz \
--cc=catalin.marinas@arm.com \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.