From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: linux-next: build warning after merge of the arm64 tree
Date: Tue, 24 Jul 2018 09:05:45 +1000 [thread overview]
Message-ID: <20180724090545.2270d975@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
Hi all,
After merging the arm64 tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/acpi/Kconfig:6:error: recursive dependency detected!
drivers/acpi/Kconfig:6: symbol ACPI depends on EFI
arch/x86/Kconfig:1920: symbol EFI depends on ACPI
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
Introduced by commit
5bcd44083a08 ("drivers: acpi: add dependency of EFI for arm64")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-07-23 23:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 23:05 Stephen Rothwell [this message]
2018-07-24 0:26 ` linux-next: build warning after merge of the arm64 tree AKASHI Takahiro
2018-07-24 8:12 ` Arnd Bergmann
2018-07-24 9:30 ` Ard Biesheuvel
-- strict thread matches above, loose matches on Subject: below --
2022-03-09 11:34 Stephen Rothwell
2022-03-09 12:18 ` Will Deacon
2022-07-07 9:57 Stephen Rothwell
2022-07-07 10:28 ` Will Deacon
2023-06-13 6:23 Stephen Rothwell
2023-06-13 15:59 ` Catalin Marinas
2023-10-24 6:24 Stephen Rothwell
2023-10-24 9:55 ` Catalin Marinas
2023-10-24 13:42 ` Ard Biesheuvel
2023-10-24 16:14 ` Catalin Marinas
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=20180724090545.2270d975@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=takahiro.akashi@linaro.org \
--cc=will.deacon@arm.com \
/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).