From: Sinan Kaya <okaya@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>, X86 ML <x86@kernel.org>
Subject: Re: linux-next: Tree for Jan 16 (PCI config warning?)
Date: Wed, 16 Jan 2019 12:23:05 -0500 [thread overview]
Message-ID: <0acd12dd-b281-446e-60c9-141732d0299b@kernel.org> (raw)
In-Reply-To: <bc18898a-8619-fc46-7c42-3d51969ee7f7@infradead.org>
Hi,
On 1/16/2019 12:00 PM, Randy Dunlap wrote:
> On 1/15/19 10:38 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20190115:
>>
>
> on x86_64:
>
> when CONFIG_PCI is not enabled (via randconfig):
>
> WARNING: unmet direct dependencies detected for PCI_LOCKLESS_CONFIG
> Depends on [n]: PCI [=n]
> Selected by [y]:
> - X86 [=y]
>
>
It looks like we'll have to continue peeling the onion some more time.
Can you please attach the kernel configuration file used?
Can I assume that this tree includes Rafael's latest pm pull?
Sinan
next prev parent reply other threads:[~2019-01-16 17:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 6:38 linux-next: Tree for Jan 16 Stephen Rothwell
2019-01-16 17:00 ` linux-next: Tree for Jan 16 (PCI config warning?) Randy Dunlap
2019-01-16 17:23 ` Sinan Kaya [this message]
2019-01-16 18:06 ` Randy Dunlap
2019-01-16 20:35 ` linux-next: Tree for Jan 16 Guenter Roeck
2019-01-17 8:49 ` Ming Lei
2019-01-17 10:35 ` Ming Lei
2019-01-17 18:32 ` Guenter Roeck
2019-01-17 18:34 ` Jens Axboe
2019-01-17 21:35 ` Guenter Roeck
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=0acd12dd-b281-446e-60c9-141732d0299b@kernel.org \
--to=okaya@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=sfr@canb.auug.org.au \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).