[Intel-gfx] [PATCH 09/10] acpi: Export acpi_bus_type

[Daniel Vetter]

On Tue, Dec 22, 2015 at 04:41:17PM +0000, Tvrtko Ursulin wrote:
> 
> On 22/12/15 06:20, ankitprasad.r.sharma at intel.com wrote:
> >From: Ankitprasad Sharma <ankitprasad.r.sharma at 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 teh contents and importantly not use it to
> >store unrecoverable user data.
> >
> >Signed-off-by: Ankitprasad Sharma <ankitprasad.r.sharma at intel.com>
> >---
> >  drivers/acpi/bus.c | 1 +
> >  1 file changed, 1 insertion(+)
> >
> >diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
> >index a212cef..69509c7 100644
> >--- a/drivers/acpi/bus.c
> >+++ b/drivers/acpi/bus.c
> >@@ -814,6 +814,7 @@ struct bus_type acpi_bus_type = {
> >  	.remove		= acpi_device_remove,
> >  	.uevent		= acpi_device_uevent,
> >  };
> >+EXPORT_SYMBOL_GPL(acpi_bus_type);
> >
> >  /* --------------------------------------------------------------------------
> >                               Initialization/Cleanup
> >
> 
> For this one we'll need to find a suitable reviewer in the ACPI team.
> 
> You can use scripts/get_maintainer.pl -f drivers/acpi/bus.c to find out who
> to ask.

Best way is to take the output of that scrip and add all the
maintainers/lists as explicit Cc: entries to your patch. That way you'll
never forget to add them when resending. And yeah, we need an ack from
acpi maintainers on this one here. They might or might not prefer we wrap
up/abstract the information we actually need (rapid start or not), but
better to ask them first.

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch