From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: linux-next: build warning after merge of the i2c tree
Date: Thu, 6 Mar 2014 13:50:16 +1100 [thread overview]
Message-ID: <20140306135016.2f026cd81b41cd2474c99124@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
Hi Wolfram,
After merging the i2c tree, today's linux-next build (powerpc
ppc64_defconfig, x86_64 allmodconfig and arm multi_v7_defconfig) produced
this warning:
drivers/video/Kconfig:42:error: recursive dependency detected!
drivers/video/Kconfig:42: symbol FB is selected by DRM_KMS_FB_HELPER
drivers/gpu/drm/Kconfig:39: symbol DRM_KMS_FB_HELPER is selected by DRM_TEGRA_FBDEV
drivers/gpu/drm/tegra/Kconfig:18: symbol DRM_TEGRA_FBDEV depends on DRM_TEGRA
drivers/gpu/drm/tegra/Kconfig:1: symbol DRM_TEGRA depends on RESET_CONTROLLER
drivers/reset/Kconfig:4: symbol RESET_CONTROLLER is selected by I2C_MV64XXX
drivers/i2c/busses/Kconfig:528: symbol I2C_MV64XXX depends on I2C
drivers/i2c/Kconfig:5: symbol I2C is selected by FB_DDC
drivers/video/Kconfig:92: symbol FB_DDC is selected by FB_CYBER2000_DDC
drivers/video/Kconfig:386: symbol FB_CYBER2000_DDC depends on FB_CYBER2000
drivers/video/Kconfig:374: symbol FB_CYBER2000 depends on FB
Introduced by commit 370136bc67c3 ("i2c: mv64xxx: Add reset deassert call").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-03-06 2:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 2:50 Stephen Rothwell [this message]
2014-03-06 9:19 ` [PATCH] i2c: mv64xxx: fix circular Kconfig dependency Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2021-08-18 6:29 linux-next: build warning after merge of the i2c tree Stephen Rothwell
2021-08-18 6:54 ` Jie Deng
2021-08-18 7:04 ` Stephen Rothwell
2021-08-18 7:13 ` Jie Deng
2019-08-02 3:21 Stephen Rothwell
2019-08-02 6:04 ` Uwe Kleine-König
2019-06-11 0:25 Stephen Rothwell
2019-06-12 8:19 ` Wolfram Sang
2019-06-12 11:02 ` Mauro Carvalho Chehab
2019-06-12 11:09 ` Wolfram Sang
2019-06-12 11:48 ` Mauro Carvalho Chehab
2019-06-12 12:04 ` Wolfram Sang
2019-06-12 12:32 ` Mauro Carvalho Chehab
2019-06-12 13:15 ` Stephen Rothwell
2019-06-12 13:24 ` Wolfram Sang
2017-06-05 1:11 Stephen Rothwell
2017-06-15 1:34 ` Stephen Rothwell
2017-06-15 7:02 ` Wolfram Sang
2017-06-15 8:48 ` Stephen Rothwell
2010-03-28 23:54 Stephen Rothwell
2010-03-29 13:21 ` Jean Delvare
2010-03-29 14:12 ` Stephen Rothwell
2010-02-17 0:38 Stephen Rothwell
2010-02-17 8:34 ` Jean Delvare
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=20140306135016.2f026cd81b41cd2474c99124@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=wsa@the-dreams.de \
/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).