[<prev] [next>] [day] [month] [year] [list]
Message-ID: <a955a3bc-61f0-06a7-6afa-e812d8e34d98@web.de>
Date: Wed, 24 Jun 2020 17:25:17 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Dinghao Liu <dinghao.liu@....edu.cn>,
linux-arm-msm@...r.kernel.org, linux-media@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org,
Aditya Pakki <pakki001@....edu>,
Navid Emamdoost <emamd001@....edu>, Kangjie Lu <kjlu@....edu>,
Qiushi Wu <wu000273@....edu>, Andy Gross <agross@...nel.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Stanimir Varbanov <stanimir.varbanov@...aro.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>
Subject: Re: [PATCH v2] media: venus: core: Fix runtime PM imbalance in
venus_probe
I propose to combine two tags in the previous patch subject.
> pm_runtime_get_sync() increments the runtime PM usage counter even
> when it returns an error code. Thus a pairing decrement is needed on
> the error handling path to keep the counter balanced. For other error
> paths after this call, things are the same.
How do you think about a wording variant like the following?
Change description:
The PM runtime usage counter is incremented even if a call of
the function “pm_runtime_get_sync” failed. Thus decrement it also
in error cases so that the reference counting is kept consistent.
Add also a call of the function “pm_runtime_get_noresume”
in one if branch for the completion of the desired exception handling.
Would you like to add the tag “Fixes” to the commit message?
Regards,
Markus
Powered by blists - more mailing lists