public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux PCI <linux-pci@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Yinghai Lu <yinghai@kernel.org>, Jiang Liu <liuj97@gmail.com>
Subject: [PATCH 0/2] PCI / ACPI cleanups
Date: Mon, 08 Jul 2013 01:15:31 +0200	[thread overview]
Message-ID: <1468174.eo7i60DZFT@vostro.rjw.lan> (raw)

Hi,

These two patches clean up the ACPI part of the PCI core and ACPIPHP.

[1/2] Make bus registration and unregistration symmetric.
[2/2] Consolidate acpiphp_enumerate_slots().

They are on top of 3.10 plus my 3.11 queue (should apply on plain 3.10),
but if they look good, I'll add them to the previous ACPI dock cleanups.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

             reply	other threads:[~2013-07-07 23:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-07 23:15 Rafael J. Wysocki [this message]
2013-07-07 23:17 ` [PATCH 1/2] ACPI / PCI: Make bus registration and unregistration symmetric Rafael J. Wysocki
2013-07-07 23:19 ` [PATCH 2/2] ACPI / PCI: Consolidate acpiphp_enumerate_slots() Rafael J. Wysocki
2013-07-08 13:27 ` [PATCH 0/3] ACPI / hotplug / PCI: Rework of events handling Rafael J. Wysocki
2013-07-08 13:28   ` [PATCH 1/3] ACPI / hotplug / PCI: Always return success after adding a function Rafael J. Wysocki
2013-07-08 13:30   ` [PATCH 2/3] ACPI / hotplug / PCI: Hotplug context objects for bridges and functions Rafael J. Wysocki
2013-07-08 23:44     ` Rafael J. Wysocki
2013-07-08 13:34   ` [PATCH 3/3] ACPI / hotplug / PCI: Unified notify handler for hotplug events Rafael J. Wysocki

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=1468174.eo7i60DZFT@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=bhelgaas@google.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=liuj97@gmail.com \
    --cc=yinghai@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