From: Heiko Stuebner <heiko@sntech.de>
To: daniel@ffwll.ch, linux-rockchip@lists.infradead.org,
airlied@linux.ie, Zhang Qilong <zhangqilong3@huawei.com>,
dri-devel@lists.freedesktop.org, hjc@rock-chips.com
Cc: Heiko Stuebner <heiko@sntech.de>
Subject: Re: (subset) [PATCH -next 0/2] fix PM usage counter unbalance
Date: Sun, 30 Oct 2022 00:08:46 +0200 [thread overview]
Message-ID: <166708118166.1656095.1443296308637313004.b4-ty@sntech.de> (raw)
In-Reply-To: <20220922132107.105419-1-zhangqilong3@huawei.com>
On Thu, 22 Sep 2022 21:21:05 +0800, Zhang Qilong wrote:
> pm_runtime_get_sync will increment pm usage counter even it failed.
> Forgetting to putting operation will result in reference leak here.
> We fix it by replacing it with the newest pm_runtime_resume_and_get
> to keep usage counter balanced.
>
> Zhang Qilong (2):
> drm/rockchip: vop: fix PM usage counter unbalance in vop ops
> drm/rockchip: fix PM usage counter unbalance in poweron
>
> [...]
Applied, thanks!
[2/2] drm/rockchip: fix PM usage counter unbalance in poweron
commit: 4dba27f1a14592ac4cf71c3bc1cc1fd05dea8015
I've ignored patch1 here, as your Huawei-collegue Yuan Can
did sent a different one that catches some more occurences.
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2022-10-29 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 13:21 [PATCH -next 0/2] fix PM usage counter unbalance Zhang Qilong
2022-09-22 13:21 ` [PATCH -next 1/2] drm/rockchip: vop: fix PM usage counter unbalance in vop ops Zhang Qilong
2022-09-22 13:21 ` [PATCH -next 2/2] drm/rockchip: fix PM usage counter unbalance in poweron Zhang Qilong
2022-10-29 22:08 ` Heiko Stuebner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=166708118166.1656095.1443296308637313004.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hjc@rock-chips.com \
--cc=linux-rockchip@lists.infradead.org \
--cc=zhangqilong3@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).