From: Zhang Qilong <zhangqilong3@huawei.com>
To: <tomi.valkeinen@ti.com>, <airlied@linux.ie>, <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org
Subject: [PATCH 0/4] drm/omap: fix reference leak in runtime get ops
Date: Tue, 10 Nov 2020 20:51:04 +0800 [thread overview]
Message-ID: <20201110125108.3827430-1-zhangqilong3@huawei.com> (raw)
This series of patches fixed several usage counter leaks refer to
pm_runtime_get_sync. Many callers forget to call pm_runtime_put_noidle
when pm_runtime_get_sync failed, and we fixed it.
Zhang Qilong (4):
drm: omapdrm: dsi: fix-reference-leak-in dsi_runtime_get.
drm: omapdrm: dss: fix reference leak in dss_runtime_get
drm/omap: hdmi4: fix reference leak in hdmi_runtime_get
drm/omap: hdmi5: fix reference leak in hdmi_runtime_get
drivers/gpu/drm/omapdrm/dss/dsi.c | 8 ++++++--
drivers/gpu/drm/omapdrm/dss/dss.c | 8 ++++++--
drivers/gpu/drm/omapdrm/dss/hdmi4.c | 4 +++-
drivers/gpu/drm/omapdrm/dss/hdmi5.c | 4 +++-
4 files changed, 18 insertions(+), 6 deletions(-)
--
2.25.4
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-11-11 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 12:51 Zhang Qilong [this message]
2020-11-10 12:51 ` [PATCH 1/4] drm: omapdrm: dsi: fix-reference-leak-in dsi_runtime_get Zhang Qilong
2020-11-10 12:51 ` [PATCH 2/4] drm: omapdrm: dss: fix reference leak in dss_runtime_get Zhang Qilong
2020-11-10 12:51 ` [PATCH 3/4] drm/omap: hdmi4: fix reference leak in hdmi_runtime_get Zhang Qilong
2020-11-10 12:51 ` [PATCH 4/4] drm/omap: hdmi5: " Zhang Qilong
2020-11-10 13:07 ` [PATCH 0/4] drm/omap: fix reference leak in runtime get ops Tomi Valkeinen
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=20201110125108.3827430-1-zhangqilong3@huawei.com \
--to=zhangqilong3@huawei.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=tomi.valkeinen@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.