From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Peter Chen <peter.chen@nxp.com>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Chen-Yu Tsai <wens@csie.org>
Subject: Re: [PATCH 6/7] gpu: drm: sun4i_drv: add missing of_node_put after calling of_parse_phandle
Date: Tue, 5 Jul 2016 09:20:44 +0200 [thread overview]
Message-ID: <20160705072044.GG7643@lukather> (raw)
In-Reply-To: <1467684294-20111-7-git-send-email-peter.chen@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]
On Tue, Jul 05, 2016 at 10:04:53AM +0800, Peter Chen wrote:
> of_node_put needs to be called when the device node which is got
> from of_parse_phandle has finished using.
>
> Cc: Maxime Ripard <maxime.ripard@free-electrons.com>
> Cc: Chen-Yu Tsai <wens@csie.org>
> Signed-off-by: Peter Chen <peter.chen@nxp.com>
Applied, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-05 7:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 2:04 [PATCH 0/7] gpu: drm: remaining missing of_node_put issue fixes Peter Chen
2016-07-05 2:04 ` [PATCH 1/7] gpu: drm: rockchip_drm_drv: add missing of_node_put after calling of_parse_phandle Peter Chen
2016-07-05 2:04 ` [PATCH 2/7] gpu: drm: sti_compositor: " Peter Chen
2016-07-12 12:59 ` Benjamin Gaignard
2016-07-05 2:04 ` [PATCH 3/7] gpu: drm: sti_vdo: " Peter Chen
2016-07-12 12:59 ` Benjamin Gaignard
2016-07-05 2:04 ` [PATCH 4/7] gpu: drm: sti_hqvdp: " Peter Chen
2016-07-12 12:59 ` Benjamin Gaignard
2016-07-05 2:04 ` [PATCH 5/7] gpu: drm: sti_vtg: " Peter Chen
2016-07-12 12:59 ` Benjamin Gaignard
2016-07-05 2:04 ` [PATCH 6/7] gpu: drm: sun4i_drv: " Peter Chen
2016-07-05 7:20 ` Maxime Ripard [this message]
2016-07-05 2:04 ` [PATCH 7/7] gpu: drm: vc4_hdmi: " Peter Chen
2016-07-05 16:23 ` Eric Anholt
2016-07-12 13:47 ` Daniel Vetter
2016-07-08 1:46 ` Eric Anholt
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=20160705072044.GG7643@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.chen@nxp.com \
--cc=wens@csie.org \
/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