driver core: move the deferred probe pointer into the private area

Nothing outside of the driver core needs to get to the deferred probe
pointer, so move it inside the private area of 'struct device' so no one
tries to mess around with it.

Cc: Grant Likely <grant.likely@secretlab.ca>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

1 files changed, 0 insertions, 5 deletions

diff --git a/include/linux/device.h b/include/linux/device.h
index 22d6938ddbb4..f62e21689fdd 100644
--- a/include/linux/device.h
+++ b/include/linux/device.h
@@ -585,10 +585,6 @@ struct device_dma_parameters {
  * @mutex:      Mutex to synchronize calls to its driver.
  * @bus:        Type of bus device is on.
  * @driver:     Which driver has allocated this
- * @deferred_probe: entry in deferred_probe_list which is used to retry the
- *              binding of drivers which were unable to get all the resources
- *              needed by the device; typically because it depends on another
- *              driver getting probed first.
  * @platform_data: Platform data specific to the device.
  *              Example: For devices on custom boards, as typical of embedded
  *              and SOC based hardware, Linux often uses platform_data to point
@@ -648,7 +644,6 @@ struct device {
         struct bus_type *bus;           /* type of bus device is on */
         struct device_driver *driver;   /* which driver has allocated this
                                            device */
-        struct list_head        deferred_probe;
         void            *platform_data; /* Platform specific data, device
                                            core doesn't touch it */
         struct dev_pm_info      power;