As the IP module driver takes care of freeing its resources.

Signed-off-by: Samuel Iglesias Gonsálvez <sigles...@igalia.com>
---
 drivers/staging/ipack/bridges/tpci200.c |    1 -
 drivers/staging/ipack/ipack.h           |    3 ---
 2 files changed, 4 deletions(-)

diff --git a/drivers/staging/ipack/bridges/tpci200.c 
b/drivers/staging/ipack/bridges/tpci200.c
index e58e312..531dfd5 100644
--- a/drivers/staging/ipack/bridges/tpci200.c
+++ b/drivers/staging/ipack/bridges/tpci200.c
@@ -597,7 +597,6 @@ static struct ipack_bus_ops tpci200_bus_ops = {
        .unmap_space = tpci200_slot_unmap_space,
        .request_irq = tpci200_request_irq,
        .free_irq = tpci200_free_irq,
-       .remove_device = NULL,
        .get_clockrate = tpci200_get_clockrate,
        .set_clockrate = tpci200_set_clockrate,
        .get_error     = tpci200_get_error,
diff --git a/drivers/staging/ipack/ipack.h b/drivers/staging/ipack/ipack.h
index e2cbf4a..33311c7 100644
--- a/drivers/staging/ipack/ipack.h
+++ b/drivers/staging/ipack/ipack.h
@@ -113,7 +113,6 @@ struct ipack_driver {
  *     @unmap_space: unmap IP address space
  *     @request_irq: request IRQ
  *     @free_irq: free IRQ
- *     @remove_device: tell the bridge module that the device has been removed
  *     @get_clockrate: Returns the clockrate the carrier is currently
  *             communicating with the device at.
  *     @set_clockrate: Sets the clock-rate for carrier / module communication.
@@ -129,8 +128,6 @@ struct ipack_bus_ops {
        int (*unmap_space) (struct ipack_device *dev, int space);
        int (*request_irq) (struct ipack_device *dev, int vector, int 
(*handler)(void *), void *arg);
        int (*free_irq) (struct ipack_device *dev);
-       int (*remove_device) (struct ipack_device *dev);
-
        int (*get_clockrate) (struct ipack_device *dev);
        int (*set_clockrate) (struct ipack_device *dev, int mherz);
        int (*get_error) (struct ipack_device *dev);
-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to