From: Thierry Reding <thierry.reding@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: linux-next: build warning after merge of the drm-panel tree
Date: Tue, 31 Mar 2015 14:16:03 +0200 [thread overview]
Message-ID: <20150331121601.GA26483@ulmo.nvidia.com> (raw)
In-Reply-To: <20150331230355.747c30a0@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1938 bytes --]
On Tue, Mar 31, 2015 at 11:03:55PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> On Wed, 25 Mar 2015 17:20:56 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > After merging the drm-panel tree, today's linux-next build (powerpc
> > ppc64_defconfig) produced this warning:
> >
> > drivers/video/fbdev/Kconfig:5:error: recursive dependency detected!
> > drivers/video/fbdev/Kconfig:5: symbol FB is selected by DRM_KMS_FB_HELPER
> > drivers/gpu/drm/Kconfig:34: symbol DRM_KMS_FB_HELPER depends on DRM_KMS_HELPER
> > drivers/gpu/drm/Kconfig:28: symbol DRM_KMS_HELPER is selected by DRM_PTN3460
> > drivers/gpu/drm/bridge/Kconfig:6: symbol DRM_PTN3460 depends on GPIOLIB
> > drivers/gpio/Kconfig:34: symbol GPIOLIB is selected by ARCH_REQUIRE_GPIOLIB
> > drivers/gpio/Kconfig:23: symbol ARCH_REQUIRE_GPIOLIB is selected by MCU_MPC8349EMITX
> > arch/powerpc/platforms/Kconfig:350: symbol MCU_MPC8349EMITX depends on I2C
> > drivers/i2c/Kconfig:7: symbol I2C is selected by FB_DDC
> > drivers/video/fbdev/Kconfig:59: symbol FB_DDC is selected by FB_CYBER2000_DDC
> > drivers/video/fbdev/Kconfig:374: symbol FB_CYBER2000_DDC depends on FB_CYBER2000
> > drivers/video/fbdev/Kconfig:362: symbol FB_CYBER2000 depends on FB
> >
> > Introduced by commit 6a43766f6ef3 ("drm/bridge: ps8622 and ptn3460
> > depend on gpiolib").
>
> This is still going on ...
I tried turning the 'select I2C' from FB_DDC into a "depends on I2C",
which seems like the more appropriate type of dependency, but that
causes a slew of new warnings because now all of a sudden some symbols
have unmet direct dependencies.
This is really quite messy. The only solution I can think of would be to
provide stubs for all of the GPIO API so that the dependency can be
dropped again. That's a little extreme and shouldn't be necessary, but I
don't see any other way to untangle this mess, I'm afraid.
Arnd, any ideas?
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-03-31 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 6:20 linux-next: build warning after merge of the drm-panel tree Stephen Rothwell
2015-03-31 12:03 ` Stephen Rothwell
2015-03-31 12:16 ` Thierry Reding [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=20150331121601.GA26483@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=arnd@arndb.de \
--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 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).