[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1541550162.196084.199.camel@acm.org>
Date: Tue, 06 Nov 2018 16:22:42 -0800
From: Bart Van Assche <bvanassche@....org>
To: Alexander Duyck <alexander.h.duyck@...ux.intel.com>,
linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org
Cc: linux-nvdimm@...ts.01.org, tj@...nel.org,
akpm@...ux-foundation.org, linux-pm@...r.kernel.org,
jiangshanlai@...il.com, rafael@...nel.org, len.brown@...el.com,
pavel@....cz, zwisler@...nel.org, dan.j.williams@...el.com,
dave.jiang@...el.com
Subject: Re: [driver-core PATCH v5 6/9] driver core: Probe devices
asynchronously instead of the driver
On Mon, 2018-11-05 at 13:12 -0800, Alexander Duyck wrote:
> diff --git a/include/linux/device.h b/include/linux/device.h
> index fc7091d436c2..4d9a39769081 100644
> --- a/include/linux/device.h
> +++ b/include/linux/device.h
> [ ... ]
> +static inline struct device_driver *dev_get_drv_async(const struct device *dev)
> +{
> + return dev->async_probe ? dev->driver_data : NULL;
> +}
> +
> +static inline void dev_set_drv_async(struct device *dev,
> + struct device_driver *drv)
> +{
> + /*
> + * Set async_probe to true indicating we are waiting for this data to be
> + * loaded as a potential driver.
> + */
> + dev->driver_data = drv;
> + dev->async_probe = true;
> +}
Since these two new functions are only used in the driver core please move
their definition into the driver core.
Thanks,
Bart.
Powered by blists - more mailing lists