From: kishorek.kadiyala@gmail.com (kishore kadiyala)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/4] omap4 hsmmc: Fix the init if CONFIG_MMC_OMAP_HS is not set
Date: Fri, 24 Sep 2010 21:54:36 +0530 [thread overview]
Message-ID: <AANLkTikADtXK=+vi_r9c7XHbwt1UjZoJv2VndmbJEqau@mail.gmail.com> (raw)
In-Reply-To: <4C9A457B.4060500@ru.mvista.com>
On Wed, Sep 22, 2010 at 11:35 PM, Sergei Shtylyov <sshtylyov@mvista.com> wrote:
> Hello.
>
> kishore kadiyala wrote:
>
>> From: Benoit Cousson <b-cousson@ti.com>
>
>> Avoid possible crash if CONFIG_MMC_OMAP_HS is not set
>
>> Signed-off-by: Benoit Cousson <b-cousson@ti.com>
>> Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
>> ---
>> ?arch/arm/mach-omap2/board-4430sdp.c | ? ?8 +++++++-
>> ?1 files changed, 7 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/board-4430sdp.c
>> b/arch/arm/mach-omap2/board-4430sdp.c
>> index a49f285..ac8541c 100644
>> --- a/arch/arm/mach-omap2/board-4430sdp.c
>> +++ b/arch/arm/mach-omap2/board-4430sdp.c
>> @@ -240,8 +240,14 @@ static int omap4_twl6030_hsmmc_late_init(struct
>> device *dev)
>>
>> ?static __init void omap4_twl6030_hsmmc_set_late_init(struct device *dev)
>> ?{
>> - ? ? ? struct omap_mmc_platform_data *pdata = dev->platform_data;
>> + ? ? ? struct omap_mmc_platform_data *pdata;
>>
>> + ? ? ? /* dev can be null if CONFIG_MMC_OMAP_HS is not set */
>> + ? ? ? if (!dev) {
>> + ? ? ? ? ? ? ? pr_err("Failed omap4_twl6030_hsmmc_set_late_init\n");
>
> ? pr_err("Failed %s\n", __func__);
OK , will have as mentioned
>
> WBR, Sergei
Regards,
Kishore
prev parent reply other threads:[~2010-09-24 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 16:43 [PATCH v3 2/4] omap4 hsmmc: Fix the init if CONFIG_MMC_OMAP_HS is not set kishore kadiyala
2010-09-22 18:05 ` Sergei Shtylyov
2010-09-24 16:24 ` kishore kadiyala [this message]
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='AANLkTikADtXK=+vi_r9c7XHbwt1UjZoJv2VndmbJEqau@mail.gmail.com' \
--to=kishorek.kadiyala@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).