From: Lukas Wunner <lukas@wunner.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-pm@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Andreas Noever <andreas.noever@gmail.com>,
Keith Busch <keith.busch@intel.com>
Subject: Re: [PATCH v2 0/9] PCIe port PM: high gloss polish & hotplug support
Date: Fri, 18 Nov 2016 10:10:57 +0100 [thread overview]
Message-ID: <20161118091057.GA12168@wunner.de> (raw)
In-Reply-To: <20161118011515.GB25762@bhelgaas-glaptop.roam.corp.google.com>
On Thu, Nov 17, 2016 at 07:15:15PM -0600, Bjorn Helgaas wrote:
> On Fri, Oct 28, 2016 at 10:52:06AM +0200, Lukas Wunner wrote:
> > Respin of this series to polish the runtime PM support for PCIe ports
> > that was added with v4.8, and extend it to native hotplug ports:
[snip]
> I applied these to pci/pm for v4.10, thanks!
>
> I did make two changes to the changelog of the last patch: you
> mentioned the "subordinate" bus, and I changed it to "secondary". We
> have often used "subordinate" to refer to the immediately-downstream
> bus, but that's slightly confusing because in the bridge spec,
> "subordinate" means the highest bus number downstream from the bridge,
> while "secondary" refers to the immediately-downstream bridge. Am I
> making sense or confusing things more?
Indeed the secondary bus was meant here and I used "subordinate" only
because the attribute in struct pci_dev is named like this. :-)
Thanks,
Lukas
next prev parent reply other threads:[~2016-11-18 9:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 8:52 [PATCH v2 0/9] PCIe port PM: high gloss polish & hotplug support Lukas Wunner
2016-10-28 8:52 ` [PATCH v2 1/9] PCI: Don't acquire ref on parent in pci_bridge_d3_update() Lukas Wunner
2016-10-28 8:52 ` [PATCH v2 4/9] PCI: Activate runtime PM on a PCIe port only if it can suspend Lukas Wunner
2016-10-28 8:52 ` [PATCH v2 2/9] PCI: Autosense device removal in pci_bridge_d3_update() Lukas Wunner
2016-10-28 8:52 ` [PATCH v2 9/9] PCI: pciehp: Add runtime PM support for PCIe hotplug ports Lukas Wunner
2016-10-28 8:52 ` [PATCH v2 3/9] PCI: Speed up algorithm in pci_bridge_d3_update() Lukas Wunner
2016-10-28 8:52 ` [PATCH v2 6/9] PCI: Unfold conditions to block runtime PM on PCIe ports Lukas Wunner
2016-10-28 8:52 ` [PATCH v2 7/9] ACPI / hotplug / PCI: Use cached copy of PCI_EXP_SLTCAP_HPC bit Lukas Wunner
2016-10-28 8:52 ` [PATCH v2 8/9] ACPI / hotplug / PCI: Make device_is_managed_by_native_pciehp() public Lukas Wunner
2016-10-28 8:52 ` [PATCH v2 5/9] PCI: Consolidate conditions to allow runtime PM on PCIe ports Lukas Wunner
2016-11-18 1:15 ` [PATCH v2 0/9] PCIe port PM: high gloss polish & hotplug support Bjorn Helgaas
2016-11-18 9:10 ` Lukas Wunner [this message]
2016-11-18 14:03 ` Bjorn Helgaas
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=20161118091057.GA12168@wunner.de \
--to=lukas@wunner.de \
--cc=andreas.noever@gmail.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=keith.busch@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.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 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.