linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chao Xie <chao.xie@marvell.com>
To: <linux-kernel@vger.kernel.org>, <sameo@linux.intel.com>,
	<xiechao.mail@gmail.com>
Cc: Chao Xie <chao.xie@marvell.com>
Subject: [PATCH 2/4] mfd: 88pm805: Fix the bug that pdata may be NULL
Date: Mon, 29 Jul 2013 04:29:25 -0400	[thread overview]
Message-ID: <1375086567-10705-3-git-send-email-chao.xie@marvell.com> (raw)
In-Reply-To: <1375086567-10705-1-git-send-email-chao.xie@marvell.com>

User pass platform data to device, and platform data may be
NULL. Add the check for pdata.

Signed-off-by: Chao Xie <chao.xie@marvell.com>
---
 drivers/mfd/88pm805.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/mfd/88pm805.c b/drivers/mfd/88pm805.c
index 5216022..57135bb 100644
--- a/drivers/mfd/88pm805.c
+++ b/drivers/mfd/88pm805.c
@@ -243,7 +243,7 @@ static int pm805_probe(struct i2c_client *client,
 		goto err_805_init;
 	}
 
-	if (pdata->plat_config)
+	if (pdata && pdata->plat_config)
 		pdata->plat_config(chip, pdata);
 
 err_805_init:
-- 
1.7.4.1


  parent reply	other threads:[~2013-07-29  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29  8:29 [PATCH 0/4] mfd: 88pn80x: bug fix and device tree support Chao Xie
2013-07-29  8:29 ` [PATCH 1/4] mfd: 88pm800: Fix the bug that pdata may be NULL Chao Xie
2013-07-29  8:29 ` Chao Xie [this message]
2013-07-29  8:29 ` [PATCH 3/4] mfd: 88pm800: add device tree support Chao Xie
2013-07-29  8:29 ` [PATCH 4/4] mfd: 88pm805: " Chao Xie
  -- strict thread matches above, loose matches on Subject: below --
2013-08-14  8:28 [PATCH 0/4] mfd: 88pn80x: bug fix and " Chao Xie
2013-08-14  8:28 ` [PATCH 2/4] mfd: 88pm805: Fix the bug that pdata may be NULL Chao Xie

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=1375086567-10705-3-git-send-email-chao.xie@marvell.com \
    --to=chao.xie@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=xiechao.mail@gmail.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).