From: Bjorn Helgaas <helgaas@kernel.org>
To: Jon Derrick <jonathan.derrick@intel.com>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Keith Busch <keith.busch@intel.com>,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH 0/2] Fixups for mixed pcie_ports=auto and native
Date: Fri, 8 Apr 2016 11:25:17 -0500 [thread overview]
Message-ID: <20160408162517.GA15034@localhost> (raw)
In-Reply-To: <1460131280-184287-1-git-send-email-jonathan.derrick@intel.com>
On Fri, Apr 08, 2016 at 10:01:18AM -0600, Jon Derrick wrote:
> This set introduces a fixup that lets non-acpi pcie ports subscribe to
> native port services. The theory is that on an acpi system, native
> services will require acpi to release control of the port instance.
>
> Rather than failing on non-acpi devices, we should continue as if they
> were native to begin with, and try to subscribe to native services just
> the same.
>
> Jon Derrick (2):
> PCI/ACPI: Do not fail ports without ACPI entries
> PCI/PCIe: Fixups for acpi port setup not being allowed to fail
I don't know what happened, but I don't see the first patch either in
patchwork (https://patchwork.ozlabs.org/project/linux-pci/list/), the
linux-pci archives, or my own email.
Bjorn
next prev parent reply other threads:[~2016-04-08 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 16:01 [PATCH 0/2] Fixups for mixed pcie_ports=auto and native Jon Derrick
2016-04-08 16:01 ` [PATCH 2/2] PCI/PCIe: Fixups for acpi port setup not being allowed to fail Jon Derrick
2016-04-08 16:25 ` Bjorn Helgaas [this message]
2016-04-08 17:32 ` [PATCH 0/2] Fixups for mixed pcie_ports=auto and native Derrick, Jonathan
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=20160408162517.GA15034@localhost \
--to=helgaas@kernel.org \
--cc=jonathan.derrick@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.