From: subhasish@mistralsolutions.com (Subhasish Ghosh)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/7] da850: pruss board specific additions.
Date: Wed, 9 Mar 2011 09:59:04 +0530 [thread overview]
Message-ID: <54A69D4520F34B0ABD7EFF35DAEFC5DC@subhasishg> (raw)
In-Reply-To: <4D7648FB.9080904@mvista.com>
Hello,
If I don't initialize it to NULL, its getting initialized to some garbage
string.
--------------------------------------------------
From: "Sergei Shtylyov" <sshtylyov@mvista.com>
Sent: Tuesday, March 08, 2011 8:49 PM
To: "Subhasish Ghosh" <subhasish@mistralsolutions.com>
Cc: <davinci-linux-open-source@linux.davincidsp.com>;
<sachi@mistralsolutions.com>; "Russell King" <linux@arm.linux.org.uk>; "open
list" <linux-kernel@vger.kernel.org>; <m-watkins@ti.com>;
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 3/7] da850: pruss board specific additions.
> Hello.
>
> On 08-03-2011 16:57, Subhasish Ghosh wrote:
>
>> This patch adds board specific initializations and setup routines.
>
>> Signed-off-by: Subhasish Ghosh<subhasish@mistralsolutions.com>
> [...]
>
>> diff --git a/arch/arm/mach-davinci/board-da850-evm.c
>> b/arch/arm/mach-davinci/board-da850-evm.c
>> index 11f986b..c614c82 100644
>> --- a/arch/arm/mach-davinci/board-da850-evm.c
>> +++ b/arch/arm/mach-davinci/board-da850-evm.c
>> @@ -1053,6 +1053,26 @@ static __init int da850_evm_init_cpufreq(void)
>> static __init int da850_evm_init_cpufreq(void) { return 0; }
>> #endif
>>
>> +static struct da8xx_pruss_devices pruss_devices[] = {
>> + {.dev_name = NULL,},
>
> No need to explictly intialize to NULL.
>
> WBR, Sergei
next prev parent reply other threads:[~2011-03-09 4:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 13:57 [PATCH v3 0/7] pruss mfd drivers Subhasish Ghosh
2011-03-08 13:57 ` [PATCH v3 1/7] mfd: add pruss mfd driver Subhasish Ghosh
2011-03-09 11:56 ` Marc Kleine-Budde
2011-03-24 13:16 ` Subhasish Ghosh
2011-03-24 13:24 ` Marc Kleine-Budde
2011-03-24 13:41 ` Kurt Van Dijck
2011-03-11 15:28 ` Arnd Bergmann
2011-03-30 7:16 ` Subhasish Ghosh
2011-03-30 10:59 ` Arnd Bergmann
2011-04-05 6:40 ` Subhasish Ghosh
2011-03-30 9:15 ` Subhasish Ghosh
2011-03-30 11:38 ` Arnd Bergmann
2011-03-18 11:59 ` Nori, Sekhar
2011-03-18 12:39 ` Mark Brown
2011-03-22 9:35 ` Nori, Sekhar
2011-03-22 9:43 ` Nori, Sekhar
2011-03-22 16:52 ` Mark Brown
2011-03-08 13:57 ` [PATCH v3 2/7] da850: pruss platform specific additions Subhasish Ghosh
2011-03-08 15:17 ` Sergei Shtylyov
2011-03-08 13:57 ` [PATCH v3 3/7] da850: pruss board " Subhasish Ghosh
2011-03-08 15:19 ` Sergei Shtylyov
2011-03-09 4:29 ` Subhasish Ghosh [this message]
2011-03-09 11:59 ` Marc Kleine-Budde
2011-03-08 13:57 ` [PATCH v3 4/7] mfd: pruss SUART private data Subhasish Ghosh
2011-03-08 13:57 ` [PATCH v3 5/7] da850: pruss SUART board specific additions Subhasish Ghosh
2011-03-08 13:57 ` [PATCH v3 6/7] da850: pruss SUART platform " Subhasish Ghosh
2011-03-08 13:57 ` [PATCH v3 7/7] tty: add pruss SUART driver Subhasish Ghosh
2011-03-08 18:47 ` Randy Dunlap
2011-03-15 7:23 ` Subhasish Ghosh
2011-03-18 5:43 ` Subhasish Ghosh
2011-03-18 11:45 ` Alan Cox
2011-03-18 12:07 ` Arnd Bergmann
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=54A69D4520F34B0ABD7EFF35DAEFC5DC@subhasishg \
--to=subhasish@mistralsolutions.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