From: jeff.mcgee@intel.com
To: isg-gms@eclists.intel.com
Cc: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeff McGee <jeff.mcgee@intel.com>
Subject: [PATCH 10/15] acpi: Export acpi_bus_type
Date: Tue, 30 Aug 2016 09:49:05 -0700 [thread overview]
Message-ID: <20160830164910.1248-11-jeff.mcgee@intel.com> (raw)
In-Reply-To: <20160830164910.1248-1-jeff.mcgee@intel.com>
From: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
Some modules, like i915.ko, needs to detect when certain ACPI features are
active inorder to prevent corruption on contended resources.
In particular, use of BIOS RapidStart Technology may corrupt the contents of
the reserved graphics memory, due to unalarmed hibernation. In which case
i915.ko cannot assume that it (reserved gfx memory) remains unmodified and
must recreate the contents and importantly not use it to store unrecoverable
user data.
Signed-off-by: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Jeff McGee <jeff.mcgee@intel.com>
---
drivers/acpi/scan.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
index 4b22ea8..7461bab 100644
--- a/drivers/acpi/scan.c
+++ b/drivers/acpi/scan.c
@@ -1269,6 +1269,7 @@ struct bus_type acpi_bus_type = {
.remove = acpi_device_remove,
.uevent = acpi_device_uevent,
};
+EXPORT_SYMBOL_GPL(acpi_bus_type);
static void acpi_device_del(struct acpi_device *device)
{
--
2.9.3
next parent reply other threads:[~2016-08-30 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160830164910.1248-1-jeff.mcgee@intel.com>
2016-08-30 16:49 ` jeff.mcgee [this message]
2016-08-30 22:47 ` [PATCH 10/15] acpi: Export acpi_bus_type Rafael J. Wysocki
2016-08-30 23:09 ` Jeff McGee
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=20160830164910.1248-11-jeff.mcgee@intel.com \
--to=jeff.mcgee@intel.com \
--cc=ankitprasad.r.sharma@intel.com \
--cc=isg-gms@eclists.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).