From: Sinan Kaya <okaya@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 21 (acpi without CONFIG_PCI)
Date: Sat, 22 Dec 2018 01:05:22 +0100 [thread overview]
Message-ID: <783f254d-1301-fe68-bad5-a80a1b9f961b@kernel.org> (raw)
In-Reply-To: <46e896b7-426a-2df9-6eae-c851332b4e43@infradead.org>
On 12/21/2018 6:43 PM, Randy Dunlap wrote:
>> Any other issues?
> There are a few Kconfig dependency issues. Here are 2 of them:
>
>
> WARNING: unmet direct dependencies detected for VGA_ARB
> Depends on [n]: HAS_IOMEM [=y] && PCI [=n] && !S390
> Selected by [y]:
> - VGA_SWITCHEROO [=y] && HAS_IOMEM [=y] && X86 [=y] && ACPI [=y]
>
> WARNING: unmet direct dependencies detected for IOSF_MBI
> Depends on [n]: PCI [=n]
> Selected by [y]:
> - X86_INTEL_LPSS [=y] && X86 [=y] && ACPI [=y]
> Selected by [m]:
> - MMC_SDHCI_ACPI [=m] && MMC [=m] && MMC_SDHCI [=m] && ACPI [=y] && X86 [=y]
>
>
> The randconfig file for these is attached.
>
> (on x86_64; both issues are from the same .config file)
Thanks, I reproduced this. I'm getting ready to post a patch.
next prev parent reply other threads:[~2018-12-22 0:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 8:32 linux-next: Tree for Dec 21 Stephen Rothwell
2018-12-21 16:21 ` Guenter Roeck
2018-12-21 16:33 ` Ard Biesheuvel
2018-12-21 20:57 ` Florian Westphal
2018-12-22 6:43 ` Chandan Rajendra
2018-12-24 8:20 ` Greg Kroah-Hartman
2018-12-31 14:01 ` Vinod Koul
2018-12-21 16:37 ` linux-next: Tree for Dec 21 (acpi without CONFIG_PCI) Randy Dunlap
[not found] ` <CAK9iUCO_Pk3eYH+hyMuqU6weDsbzC9Sg1Z719fm8u_3Oh7s-iQ@mail.gmail.com>
2018-12-21 17:26 ` Randy Dunlap
2018-12-21 17:43 ` Randy Dunlap
2018-12-22 0:05 ` Sinan Kaya [this message]
2018-12-21 18:28 ` Randy Dunlap
2018-12-22 0:04 ` Sinan Kaya
2018-12-21 17:08 ` linux-next: Tree for Dec 21 (nvdimm/security.o) Randy Dunlap
2018-12-21 18:51 ` Dan Williams
2018-12-21 21:01 ` Dan Williams
2018-12-21 17:35 ` linux-next: Tree for Dec 21 (mmc/host/sdhci-omap.c) Randy Dunlap
2018-12-21 18:02 ` linux-next: Tree for Dec 21 (SND_HDA_INTEL_DSP_DETECTION) Randy Dunlap
2018-12-21 20:39 ` [alsa-devel] " Pierre-Louis Bossart
2018-12-21 18:36 ` linux-next: Tree for Dec 21 (FB_BACKLIGHT) Randy Dunlap
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=783f254d-1301-fe68-bad5-a80a1b9f961b@kernel.org \
--to=okaya@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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).