staging: virtpci: Remove no-op suspend/resume functions

The virtpci bus driver still uses the legacy suspend/resume callbacks. In
their current implementation these callbacks only contain a macro that
always expands to 'do { } while(0)'. So instead of converting them to dev PM
ops just remove them.

Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

diff --git a/drivers/staging/unisys/virtpci/virtpci.c b/drivers/staging/unisys/virtpci/virtpci.c
index 729affc85a870bea9ae219c9cd143ccb5b9beb49..8fdfd6f3605f0b1bcdfccc7fe8df607bec7a577f 100644 (file)
--- a/drivers/staging/unisys/virtpci/virtpci.c
+++ b/drivers/staging/unisys/virtpci/virtpci.c
@@ -104,8 +104,6 @@ static ssize_t virtpci_driver_attr_store(struct kobject *kobj,
                                         const char *buf, size_t count);
 static int virtpci_bus_match(struct device *dev, struct device_driver *drv);
 static int virtpci_uevent(struct device *dev, struct kobj_uevent_env *env);
-static int virtpci_device_suspend(struct device *dev, pm_message_t state);
-static int virtpci_device_resume(struct device *dev);
 static int virtpci_device_probe(struct device *dev);
 static int virtpci_device_remove(struct device *dev);
 
@@ -128,8 +126,6 @@ static struct bus_type virtpci_bus_type = {
        .name = "uisvirtpci",
        .match = virtpci_bus_match,
        .uevent = virtpci_uevent,
-       .suspend = virtpci_device_suspend,
-       .resume = virtpci_device_resume,
 };
 
 static struct device virtpci_rootbus_device = {
@@ -757,18 +753,6 @@ static int virtpci_uevent(struct device *dev, struct kobj_uevent_env *env)
        return 0;
 }
 
-static int virtpci_device_suspend(struct device *dev, pm_message_t state)
-{
-       DBGINF("In virtpci_device_suspend -NYI ****\n");
-       return 0;
-}
-
-static int virtpci_device_resume(struct device *dev)
-{
-       DBGINF("In virtpci_device_resume -NYI ****\n");
-       return 0;
-}
-
 /* For a child device just created on a client bus, fill in
  * information about the driver that is controlling this device into
  * the appropriate slot within the vbus channel of the bus