[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <791408d3-bf97-0f54-adc5-9b06540015c6@oracle.com>
Date: Thu, 8 Nov 2018 14:43:04 -0800
From: jane.chu@...cle.com
To: Alexander Duyck <alexander.h.duyck@...ux.intel.com>,
linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org
Cc: len.brown@...el.com, bvanassche@....org, linux-pm@...r.kernel.org,
rafael@...nel.org, jiangshanlai@...il.com,
linux-nvdimm@...ts.01.org, pavel@....cz, zwisler@...nel.org,
tj@...nel.org, akpm@...ux-foundation.org
Subject: Re: [driver-core PATCH v6 3/9] device core: Consolidate locking and
unlocking of parent and device
Hi, Alex,
On 11/08/2018 10:06 AM, Alexander Duyck wrote:
> +/*
> + * __device_driver_lock - release locks needed to manipulate dev->drv
You meant to say __device_driver_unlock, right?
> + * @dev: Device we will update driver info for
> + * @parent: Parent device. Needed if the bus requires parent lock
> + *
> + * This function will release the required locks for manipulating dev->drv.
> + * Normally this will just be the the @dev lock, but when called for a
> + * USB interface, @parent lock will be released as well.
> + */
> +static void __device_driver_unlock(struct device *dev, struct device *parent)
> +{
> + device_unlock(dev);
> + if (parent && dev->bus->need_parent_lock)
> + device_unlock(parent);
> +}
-jane
Powered by blists - more mailing lists