public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] ACPI / OSL: Allow PCI to be disabled
Date: Tue, 11 Dec 2018 18:00:19 -0500	[thread overview]
Message-ID: <edc8afd7-64a0-a143-e8d6-df3b14b21753@kernel.org> (raw)
In-Reply-To: <CAJZ5v0i+rgLL+KrRs69URbGhUxDK9eUEuLifDWuL2mgpkAv_1g@mail.gmail.com>

On 12/11/2018 5:51 PM, Rafael J. Wysocki wrote:
> Well, users running kernels with CONFIG_PCI unset on platforms
> expecting PCI support to be present in the OS may want to know that I
> suppose, so that would be a good reason to return an error, but
> perhaps just once rather than on every access (maybe unless debugging
> is enabled?).

Warning once would be a good trade-off.

  reply	other threads:[~2018-12-11 23:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 18:13 [PATCH v3 1/3] ACPI: Allow PCI to be disabled for reboot Sinan Kaya
2018-12-10 18:13 ` [PATCH v3 2/3] ACPI / OSL: Allow PCI to be disabled Sinan Kaya
2018-12-11 10:07   ` Rafael J. Wysocki
2018-12-11 16:52     ` Sinan Kaya
2018-12-11 17:09   ` Christoph Hellwig
2018-12-11 17:37     ` Sinan Kaya
2018-12-11 21:46       ` Rafael J. Wysocki
2018-12-11 21:57         ` Sinan Kaya
2018-12-11 22:16           ` Rafael J. Wysocki
2018-12-11 22:22             ` Sinan Kaya
2018-12-11 22:51               ` Rafael J. Wysocki
2018-12-11 23:00                 ` Sinan Kaya [this message]
2018-12-10 18:13 ` [PATCH v3 3/3] PCI/ACPI: Allow ACPI to be built without PCI support Sinan Kaya

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=edc8afd7-64a0-a143-e8d6-df3b14b21753@kernel.org \
    --to=okaya@kernel.org \
    --cc=hch@infradead.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    /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