From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [PATCH 0/4] ACPI: Reorganize the core device management/enumeration code
Date: Tue, 14 Jul 2015 01:16:12 +0200 [thread overview]
Message-ID: <4521894.N8pXmo8fxI@vostro.rjw.lan> (raw)
Hi,
The size and complexity of drivers/acpi/scan.c has bothered me for quite
a while and since I'm working on a feature that will benefit from exposing
some additional information under ACPI device objects in sysfs, I've decided
to reorganize the code to move some things out of scan.c.
[1/4] Move all ACPI device code related to sysfs into a separate (new) file.
[2/4] Move device matching code to bus.c.
[3/4] Mode device notification, bus operations and driver management code to bus.c.
[4/4] Register the ACPI bus type in acpi_bus_init().
No functional changes except for the [4/4] that will case ACPI to be disabled if
the ACPI bus type cannot be registered.
Thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next reply other threads:[~2015-07-13 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 23:16 Rafael J. Wysocki [this message]
2015-07-13 23:17 ` [PATCH 1/4] ACPI / scan: Mode sysfs-related device code to a separate file Rafael J. Wysocki
2015-07-13 23:18 ` [PATCH 2/4] ACPI / scan: Mode device matching code to bus.c Rafael J. Wysocki
2015-07-13 23:18 ` [PATCH 3/4] ACPI / scan: Mode bus operations and notification routines " Rafael J. Wysocki
2015-07-13 23:19 ` [PATCH 4/4] ACPI / bus: Move ACPI bus type registration Rafael J. Wysocki
2015-07-30 9:54 ` [PATCH 0/4] ACPI: Reorganize the core device management/enumeration code Mika Westerberg
2015-08-01 1:19 ` 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=4521894.N8pXmo8fxI@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox