From: Shawn Guo <shawnguo@kernel.org>
To: zhong jiang <zhongjiang@huawei.com>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpu: do not double put device node in zx_drm_probe
Date: Mon, 27 Aug 2018 15:18:26 +0800 [thread overview]
Message-ID: <20180827071824.GG3850@dragon> (raw)
In-Reply-To: <1534472646-10368-1-git-send-email-zhongjiang@huawei.com>
On Fri, Aug 17, 2018 at 10:24:06AM +0800, zhong jiang wrote:
> for_each_available_child_of_node will get and put the node properly,
> the following of_node_put will lead to the double put. So just
> remove it.
>
> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
Acked-by: Shawn Guo <shawnguo@kernel.org>
next prev parent reply other threads:[~2018-08-27 7:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 2:24 [PATCH] gpu: do not double put device node in zx_drm_probe zhong jiang
2018-08-23 11:41 ` zhong jiang
2018-08-27 7:18 ` Shawn Guo [this message]
2018-09-18 15:19 ` Daniel Vetter
2018-09-19 21:32 ` Shawn Guo
2018-09-06 14:51 ` zhong jiang
2018-09-18 14:59 ` zhong jiang
2018-09-18 15:02 ` Greg KH
2018-09-18 15:18 ` zhong jiang
2018-09-18 15:20 ` Daniel Vetter
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=20180827071824.GG3850@dragon \
--to=shawnguo@kernel.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhongjiang@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).