linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "MyungJoo Ham" <myungjoo.ham@samsung.com>
To: "Peter Chen" <peter.chen@nxp.com>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>
Cc: "Kyungmin Park" <kyungmin.park@samsung.com>
Subject: RE: [PATCH 6/7] devfreq: add missing of_node_put after calling of_parse_phandle
Date: Wed, 06 Jul 2016 02:38:01 +0000	[thread overview]
Message-ID: <1979940416.433337.1467772681910.JavaMail.weblogic@ep2ml104d> (raw)
In-Reply-To: CGME20160701094923epcas1p164cc8773ec44a00dfc506a6192df3409@epcas1p1.samsung.com

[-- Attachment #1: Type: text/plain, Size: 554 bytes --]

> --------- Original Message ---------
> Sender : Peter Chen <peter.chen@nxp.com>
> Date   : 2016-07-01 18:49 (GMT+9)
> Title  : [PATCH 6/7] devfreq: add missing of_node_put after calling of_parse_phandle
>  
> of_node_put needs to be called when the device node which is got
> from of_parse_phandle has finished using.
>  
> Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
> Cc: Kyungmin Park <kyungmin.park@samsung.com>
> Signed-off-by: Peter Chen <peter.chen@nxp.com>

Thank you!


Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>


  parent reply	other threads:[~2016-07-06  2:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1467366121-14120-1-git-send-email-peter.chen@nxp.com>
2016-07-01  9:41 ` [PATCH 1/7] extcon: add missing of_node_put after calling of_parse_phandle Peter Chen
2016-07-02  4:46   ` Chanwoo Choi
2016-07-01  9:41 ` [PATCH 2/7] arm: mach-shmobile: pm-rmobile: " Peter Chen
2016-07-01 12:31   ` Geert Uytterhoeven
2016-07-04  2:10     ` Peter Chen
2016-07-01  9:41 ` [PATCH 3/7] arm: mach-u300: regulator: " Peter Chen
2016-07-01  9:41 ` Peter Chen
2016-07-01  9:41 ` Peter Chen
2016-07-01  9:41 ` Peter Chen
2016-07-01  9:41 ` [PATCH 4/7] bus: arm-cci: " Peter Chen
2016-07-01 10:29   ` Suzuki K Poulose
2016-07-01 10:33     ` Will Deacon
2016-07-04  2:48       ` Peter Chen
2016-07-04  9:19         ` Will Deacon
2016-07-01  9:41 ` [PATCH 5/7] bus: vexpress-config: " Peter Chen
2016-07-11  9:02   ` Liviu Dudau
2016-07-01  9:42 ` [PATCH 6/7] devfreq: " Peter Chen
2016-07-01  9:42 ` [PATCH 7/7] devfreq: exynos-bus: " Peter Chen
2016-07-02  4:53   ` Chanwoo Choi
     [not found] ` <1467366121-14120-4-git-send-email-peter.chen@nxp.com>
2016-07-05 21:24   ` [PATCH 3/7] arm: mach-u300: regulator: " Linus Walleij
     [not found] ` <CGME20160701094923epcas1p164cc8773ec44a00dfc506a6192df3409@epcas1p1.samsung.com>
2016-07-06  2:38   ` MyungJoo Ham [this message]
     [not found] ` <CGME20160701094927epcas1p43f956ee3465f96e2f9c99b44c0f5b49d@epcas1p4.samsung.com>
2016-07-06  2:47   ` [PATCH 7/7] devfreq: exynos-bus: " MyungJoo Ham

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=1979940416.433337.1467772681910.JavaMail.weblogic@ep2ml104d \
    --to=myungjoo.ham@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=peter.chen@nxp.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).