From: Peter Chen <peter.chen@nxp.com>
To: <ssantosh@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, Peter Chen <peter.chen@nxp.com>
Subject: [PATCH 1/1] memory: emif: add missing of_node_put after calling of_parse_phandle
Date: Fri, 15 Jul 2016 17:35:10 +0800 [thread overview]
Message-ID: <1468575310-25018-1-git-send-email-peter.chen@nxp.com> (raw)
of_node_put needs to be called when the device node which is got
from of_parse_phandle has finished using.
Signed-off-by: Peter Chen <peter.chen@nxp.com>
---
drivers/memory/emif.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/memory/emif.c b/drivers/memory/emif.c
index 04644e7..c5ec77d 100644
--- a/drivers/memory/emif.c
+++ b/drivers/memory/emif.c
@@ -1409,8 +1409,10 @@ static struct emif_data * __init_or_module of_get_memory_device_details(
goto out;
error:
+ of_put_node(np_ddr);
return NULL;
out:
+ of_put_node(np_ddr);
return emif;
}
--
1.9.1
next reply other threads:[~2016-07-15 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 9:35 Peter Chen [this message]
2016-07-15 18:50 ` [PATCH 1/1] memory: emif: add missing of_node_put after calling of_parse_phandle kbuild test robot
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=1468575310-25018-1-git-send-email-peter.chen@nxp.com \
--to=peter.chen@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ssantosh@kernel.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;
as well as URLs for NNTP newsgroup(s).