From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>, DRI <dri-devel@lists.freedesktop.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: linux-next: build failure after merge of the drm tree
Date: Tue, 5 Nov 2019 13:54:22 +1100 [thread overview]
Message-ID: <20191105135422.46ddc865@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
Hi all,
After merging the drm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/platforms/embedded6xx/Kconfig:2:error: recursive dependency detected!
arch/powerpc/platforms/embedded6xx/Kconfig:2: symbol EMBEDDED6xx depends on BROKEN_ON_SMP
init/Kconfig:79: symbol BROKEN_ON_SMP depends on BROKEN
init/Kconfig:76: symbol BROKEN is selected by DRM_I915_DEBUG
drivers/gpu/drm/i915/Kconfig.debug:20: symbol DRM_I915_DEBUG depends on DRM_I915
drivers/gpu/drm/i915/Kconfig:2: symbol DRM_I915 depends on DRM
drivers/gpu/drm/Kconfig:8: symbol DRM depends on AGP
drivers/char/agp/Kconfig:2: symbol AGP depends on PCI
drivers/pci/Kconfig:16: symbol PCI depends on HAVE_PCI
drivers/pci/Kconfig:7: symbol HAVE_PCI is selected by FORCE_PCI
drivers/pci/Kconfig:11: symbol FORCE_PCI is selected by MVME5100
arch/powerpc/platforms/embedded6xx/Kconfig:51: symbol MVME5100 depends on EMBEDDED6xx
For a resolution refer to Documentation/kbuild/kconfig-language.rst
subsection "Kconfig recursive dependency limitations"
Caused by commit
d9d54a530a70 ("drm/i915: Put future HW and their uAPIs under STAGING & BROKEN")
You really should not select BROKEN. It is assumed to always be false
so we can make actually broken code depend on it (and therefore not
be built).
I have used the drm tree from next-20191031 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>, DRI <dri-devel@lists.freedesktop.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build failure after merge of the drm tree
Date: Tue, 5 Nov 2019 13:54:22 +1100 [thread overview]
Message-ID: <20191105135422.46ddc865@canb.auug.org.au> (raw)
Message-ID: <20191105025422.BGPkvwv8gF2sdhIUfOYqut40tfC2DhGm1RchWULUqmo@z> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1439 bytes --]
Hi all,
After merging the drm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/platforms/embedded6xx/Kconfig:2:error: recursive dependency detected!
arch/powerpc/platforms/embedded6xx/Kconfig:2: symbol EMBEDDED6xx depends on BROKEN_ON_SMP
init/Kconfig:79: symbol BROKEN_ON_SMP depends on BROKEN
init/Kconfig:76: symbol BROKEN is selected by DRM_I915_DEBUG
drivers/gpu/drm/i915/Kconfig.debug:20: symbol DRM_I915_DEBUG depends on DRM_I915
drivers/gpu/drm/i915/Kconfig:2: symbol DRM_I915 depends on DRM
drivers/gpu/drm/Kconfig:8: symbol DRM depends on AGP
drivers/char/agp/Kconfig:2: symbol AGP depends on PCI
drivers/pci/Kconfig:16: symbol PCI depends on HAVE_PCI
drivers/pci/Kconfig:7: symbol HAVE_PCI is selected by FORCE_PCI
drivers/pci/Kconfig:11: symbol FORCE_PCI is selected by MVME5100
arch/powerpc/platforms/embedded6xx/Kconfig:51: symbol MVME5100 depends on EMBEDDED6xx
For a resolution refer to Documentation/kbuild/kconfig-language.rst
subsection "Kconfig recursive dependency limitations"
Caused by commit
d9d54a530a70 ("drm/i915: Put future HW and their uAPIs under STAGING & BROKEN")
You really should not select BROKEN. It is assumed to always be false
so we can make actually broken code depend on it (and therefore not
be built).
I have used the drm tree from next-20191031 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-11-05 2:54 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 2:54 Stephen Rothwell [this message]
2019-11-05 2:54 ` linux-next: build failure after merge of the drm tree Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2026-08-10 15:03 Mark Brown
2026-08-14 14:45 ` Mark Brown
2026-06-16 13:14 Mark Brown
2026-06-16 14:01 ` Vlastimil Babka (SUSE)
2026-06-16 14:12 ` Mark Brown
2026-06-03 13:32 Mark Brown
2026-03-10 15:25 Mark Brown
2026-03-10 15:36 ` Jacob Moroni
2026-03-10 15:42 ` Christian König
2026-02-10 21:08 Mark Brown
2025-12-04 4:24 Stephen Rothwell
2025-12-04 13:49 ` Alex Deucher
2025-04-28 3:30 Stephen Rothwell
2025-04-28 3:57 ` Dave Airlie
2025-04-28 4:24 ` Stephen Rothwell
2024-07-01 9:13 Stephen Rothwell
2024-07-01 17:19 ` Nathan Chancellor
2024-07-12 2:28 ` Stephen Rothwell
2024-07-12 3:12 ` David Airlie
2023-04-11 6:47 Stephen Rothwell
2023-01-19 2:12 Stephen Rothwell
[not found] <20220930105434.111407-1-broonie@kernel.org>
2022-10-04 2:20 ` Stephen Rothwell
2022-10-04 2:24 ` David Airlie
2022-10-04 3:05 ` Stephen Rothwell
2022-10-04 11:39 ` Mark Brown
2022-10-05 15:30 ` Alex Deucher
2022-10-05 16:45 ` Hamza Mahfooz
2022-10-05 22:28 ` Stephen Rothwell
2022-10-06 8:12 ` Stephen Rothwell
2022-10-06 13:56 ` Alex Deucher
2022-10-06 16:52 ` Stephen Rothwell
2022-10-06 16:25 ` Hamza Mahfooz
2022-02-25 16:42 broonie
2022-02-28 3:46 ` Stephen Rothwell
2022-02-28 6:44 ` Hsin-Yi Wang
2022-02-28 6:48 ` Dave Airlie
2022-02-28 15:33 ` Robert Foss
2022-03-01 6:58 ` Dave Airlie
2021-08-20 2:33 Stephen Rothwell
2021-08-20 6:23 ` Masahiro Yamada
2021-09-01 21:50 ` Stephen Rothwell
2021-09-05 22:49 ` Stephen Rothwell
2021-09-06 7:34 ` Daniel Vetter
2021-09-08 3:13 ` Masahiro Yamada
2021-09-08 9:07 ` Daniel Vetter
2021-04-09 3:36 Stephen Rothwell
2021-01-08 0:55 Stephen Rothwell
2021-01-08 1:25 ` Stephen Rothwell
2021-01-10 23:56 ` Stephen Rothwell
2021-01-18 0:59 ` Stephen Rothwell
2021-01-18 1:06 ` Dave Airlie
2021-01-20 12:12 ` Daniel Vetter
2021-01-20 20:44 ` Stephen Rothwell
2020-12-09 1:53 Stephen Rothwell
2020-09-28 3:54 Stephen Rothwell
[not found] ` <20200928060427.GA15041@lst.de>
2020-09-28 6:08 ` Dave Airlie
2020-09-28 10:15 ` Paul Cercueil
[not found] ` <20200928113415.GA555@lst.de>
2020-09-28 11:46 ` Paul Cercueil
[not found] ` <20200928121002.GA3219@lst.de>
2020-09-28 13:31 ` Paul Cercueil
[not found] ` <20200930090252.GA9357@lst.de>
2020-09-30 13:33 ` Paul Cercueil
[not found] ` <20200930161124.GA6859@lst.de>
2020-09-30 16:39 ` Paul Cercueil
[not found] ` <20200930164023.GA8645@lst.de>
2020-09-30 16:45 ` Paul Cercueil
2020-05-08 4:29 Stephen Rothwell
2019-10-10 0:22 Stephen Rothwell
2019-07-08 4:48 Stephen Rothwell
2019-04-26 2:17 Stephen Rothwell
2018-05-16 6:53 Stephen Rothwell
2018-05-16 8:09 ` Oded Gabbay
2018-05-17 5:00 ` Dave Airlie
2018-03-13 5:46 Stephen Rothwell
2018-01-02 1:48 Stephen Rothwell
2017-03-20 0:51 Stephen Rothwell
2017-03-20 8:03 ` Daniel Vetter
2017-03-20 8:05 ` Daniel Vetter
2016-07-15 3:40 Stephen Rothwell
2016-07-15 4:32 ` Sedat Dilek
2016-04-28 1:57 Stephen Rothwell
2016-04-28 8:11 ` Jani Nikula
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=20191105135422.46ddc865@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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