[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190212140924.GA14444@kroah.com>
Date: Tue, 12 Feb 2019 15:09:24 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: LKML <linux-kernel@...r.kernel.org>,
Linux PM <linux-pm@...r.kernel.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
Daniel Vetter <daniel@...ll.ch>,
Lukas Wunner <lukas@...ner.de>,
Andrzej Hajda <a.hajda@...sung.com>,
Russell King - ARM Linux <linux@...linux.org.uk>,
Lucas Stach <l.stach@...gutronix.de>,
Linus Walleij <linus.walleij@...aro.org>,
Thierry Reding <thierry.reding@...il.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: [PATCH 0/2] driver core: Fixes related to device links
On Tue, Feb 12, 2019 at 01:01:13PM +0100, Rafael J. Wysocki wrote:
> Hi Greg at al,
>
> These fix two issues on top of the recent device links material in
> driver-core/driver-core-next.
>
> The first one fixes a race condition that may trigger when
> __pm_runtime_set_status() is used incorrectly (that is, when it is
> called with PM-runtime enabled for the target device and working).
>
> The second one fixes a supplier PM-runtime usage counter imbalance
> resulting from adding and removing (e.g. in the error code path) a
> stateless device link to it from within the consumer driver's probe
> callback.
>
> Please refer to the patch changelogs for details.
Looks good, all now queued up, thanks.
greg k-h
Powered by blists - more mailing lists