From: Eric Anholt <eric@anholt.net>
To: Wen Yang <wen.yang99@zte.com.cn>, linux-kernel@vger.kernel.org
Cc: wang.yi59@zte.com.cn, Wen Yang <wen.yang99@zte.com.cn>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
"open list\:DRM DRIVERS" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 5/7] drm/pl111: fix possible object reference leak
Date: Thu, 04 Apr 2019 12:59:15 -0700 [thread overview]
Message-ID: <874l7dwnho.fsf@anholt.net> (raw)
In-Reply-To: <1554307455-40361-6-git-send-email-wen.yang99@zte.com.cn>
[-- Attachment #1: Type: text/plain, Size: 237 bytes --]
Wen Yang <wen.yang99@zte.com.cn> writes:
> The call to of_find_matching_node_and_match returns a node pointer with
> refcount incremented thus it must be explicitly decremented after the
> last usage.
Pushed to drm-misc-next. Thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Eric Anholt <eric@anholt.net>
To: linux-kernel@vger.kernel.org
Cc: wang.yi59@zte.com.cn, Wen Yang <wen.yang99@zte.com.cn>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 5/7] drm/pl111: fix possible object reference leak
Date: Thu, 04 Apr 2019 12:59:15 -0700 [thread overview]
Message-ID: <874l7dwnho.fsf@anholt.net> (raw)
In-Reply-To: <1554307455-40361-6-git-send-email-wen.yang99@zte.com.cn>
[-- Attachment #1: Type: text/plain, Size: 237 bytes --]
Wen Yang <wen.yang99@zte.com.cn> writes:
> The call to of_find_matching_node_and_match returns a node pointer with
> refcount incremented thus it must be explicitly decremented after the
> last usage.
Pushed to drm-misc-next. Thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-04-04 19:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 16:04 [PATCH 0/7] fix possible object reference leaks in drivers/gpu Wen Yang
2019-04-03 16:04 ` [PATCH 1/7] drm/mediatek: fix possible object reference leak Wen Yang
2019-04-03 16:04 ` Wen Yang
2019-04-09 5:15 ` CK Hu
2019-04-09 5:15 ` CK Hu
2019-04-09 5:15 ` CK Hu
2019-04-03 16:04 ` [PATCH 2/7] drm/meson: " Wen Yang
2019-04-03 16:04 ` Wen Yang
2019-04-03 16:04 ` Wen Yang
2019-04-03 16:04 ` Wen Yang
2019-04-04 20:05 ` Markus Elfring
2019-04-04 20:05 ` Markus Elfring
2019-04-04 20:05 ` Markus Elfring
2019-04-04 20:05 ` Markus Elfring
2019-04-04 20:05 ` Markus Elfring
2019-04-03 16:04 ` [PATCH 3/7] drm/msm: a5xx: " Wen Yang
2019-04-10 16:21 ` Jordan Crouse
2019-04-10 16:21 ` Jordan Crouse
2019-04-03 16:04 ` [PATCH 4/7] drm/omap: " Wen Yang
2019-04-04 13:25 ` Laurent Pinchart
2019-04-08 1:24 ` wen.yang99
2019-04-04 20:42 ` Markus Elfring
2019-04-04 20:42 ` Markus Elfring
2019-04-03 16:04 ` [PATCH 5/7] drm/pl111: " Wen Yang
2019-04-03 16:04 ` Wen Yang
2019-04-04 19:59 ` Eric Anholt [this message]
2019-04-04 19:59 ` Eric Anholt
2019-04-04 21:05 ` Markus Elfring
2019-04-04 21:05 ` Markus Elfring
2019-04-03 16:04 ` [PATCH 6/7] drm: rcar-du: " Wen Yang
2019-04-04 13:35 ` Laurent Pinchart
2019-04-08 1:10 ` 答复: " wen.yang99
2019-04-03 16:04 ` [PATCH 7/7] drm/tegra: " Wen Yang
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=874l7dwnho.fsf@anholt.net \
--to=eric@anholt.net \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wang.yi59@zte.com.cn \
--cc=wen.yang99@zte.com.cn \
/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.