From: Jason Jin <Jason.jin@freescale.com>
To: galak@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, Jason Jin <Jason.jin@freescale.com>
Subject: [PATCH] Minor fixes for 85xxds and 8536ds board.
Date: Wed, 9 Jul 2008 09:27:35 +0800 [thread overview]
Message-ID: <1215566855-6198-1-git-send-email-Jason.jin@freescale.com> (raw)
Remove the "uninitialized use" compile warning and
avoid potential runtime issue.
Signed-off-by: Jason Jin <Jason.jin@freescale.com>
---
arch/powerpc/platforms/85xx/mpc8536_ds.c | 2 +-
arch/powerpc/platforms/85xx/mpc85xx_ds.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/platforms/85xx/mpc8536_ds.c b/arch/powerpc/platforms/85xx/mpc8536_ds.c
index 9943816..69e2129 100644
--- a/arch/powerpc/platforms/85xx/mpc8536_ds.c
+++ b/arch/powerpc/platforms/85xx/mpc8536_ds.c
@@ -40,7 +40,7 @@ void __init mpc8536_ds_pic_init(void)
struct resource r;
struct device_node *np;
- np = of_find_node_by_type(np, "open-pic");
+ np = of_find_node_by_type(NULL, "open-pic");
if (np == NULL) {
printk(KERN_ERR "Could not find open-pic node\n");
return;
diff --git a/arch/powerpc/platforms/85xx/mpc85xx_ds.c b/arch/powerpc/platforms/85xx/mpc85xx_ds.c
index 8b2d63d..25f41cd 100644
--- a/arch/powerpc/platforms/85xx/mpc85xx_ds.c
+++ b/arch/powerpc/platforms/85xx/mpc85xx_ds.c
@@ -64,7 +64,7 @@ void __init mpc85xx_ds_pic_init(void)
int cascade_irq;
#endif
- np = of_find_node_by_type(np, "open-pic");
+ np = of_find_node_by_type(NULL, "open-pic");
if (np == NULL) {
printk(KERN_ERR "Could not find open-pic node\n");
return;
--
1.5.4
next reply other threads:[~2008-07-09 1:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 1:27 Jason Jin [this message]
[not found] <1215480068-6235-1-git-send-email-Jason.jin@freescale.com>
2008-07-09 13:00 ` [PATCH] Minor fixes for 85xxds and 8536ds board Kumar Gala
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=1215566855-6198-1-git-send-email-Jason.jin@freescale.com \
--to=jason.jin@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).