ACPI / hotplug / PCI: Drop flags field from struct acpiphp_bridge

The only bridge flag used by the ACPI-based PCI hotplug (ACPIPHP)
code is BRIDGE_HAS_EJ0, but it is only used by the event handling
function hotplug_event() and if that flag is set, the corresponding
function flag FUNC_HAS_EJ0 is set as well, so that bridge flag is
redundant.

For this reason, drop BRIDGE_HAS_EJ0 and all code referring to it
and since it is the only bridge flag defined, drop the flags field
from struct acpiphp_bridge entirely.

Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>

1 files changed, 0 insertions, 9 deletions

diff --git a/drivers/pci/hotplug/acpiphp_glue.c b/drivers/pci/hotplug/acpiphp_glue.c
index a251071b7d79..5d79175b9a09 100644
--- a/drivers/pci/hotplug/acpiphp_glue.c
+++ b/drivers/pci/hotplug/acpiphp_glue.c
@@ -986,9 +986,6 @@ static void hotplug_event(acpi_handle handle, u32 type, void *data)
         case ACPI_NOTIFY_EJECT_REQUEST:
                 /* request device eject */
                 dbg("%s: Device eject notify on %s\n", __func__, objname);
-                if (bridge && !(bridge->flags & BRIDGE_HAS_EJ0))
-                        break;
-
                 if (!(acpiphp_disable_slot(func->slot)))
                         acpiphp_eject_slot(func->slot);
 
@@ -1125,12 +1122,6 @@ void acpiphp_enumerate_slots(struct pci_bus *bus)
                 mutex_unlock(&acpiphp_context_lock);
         }
 
-        status = acpi_get_handle(bridge->handle, "_EJ0", &handle);
-        if (ACPI_SUCCESS(status)) {
-                dbg("found ejectable p2p bridge\n");
-                bridge->flags |= BRIDGE_HAS_EJ0;
-        }
-
         /* must be added to the list prior to calling register_slot */
         mutex_lock(&bridge_mutex);
         list_add(&bridge->list, &bridge_list);