From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 2/2] mucmc52, uc101: delete ata@3a00 node, if no CF card is detected
Date: Mon, 14 Sep 2009 17:55:01 +0200 [thread overview]
Message-ID: <4AAE6755.5060205@denx.de> (raw)
In-Reply-To: <200909141729.56736.sr@denx.de>
Hello Stefan,
Stefan Roese wrote:
> On Monday 14 September 2009 17:26:45 Heiko Schocher wrote:
[...]
>>>> do_fixup_by_path_u32(blob, cpu_path, "timebase-frequency", OF_TBCLK,
>>>> 1); do_fixup_by_path_u32(blob, cpu_path, "bus-frequency",
>>>> bd->bi_busfreq, 1); @@ -137,6 +140,21 @@ void ft_cpu_setup(void *blob,
>>>> bd_t *bd)
>>>> do_fixup_by_path(blob, eth_path, "mac-address", enetaddr, 6, 0);
>>>> do_fixup_by_path(blob, eth_path, "local-mac-address", enetaddr, 6, 0);
>>>> #endif
>>>> +#if defined(CONFIG_OF_IDE_FIXUP)
>>>> + if (ide_dev_desc[0].type == DEV_TYPE_UNKNOWN) {
>>>> + /* NO CF card detected -> delete ata node in DTS */
>>>> + int nodeoffset = 0;
>>>> + char nodename[] = "/soc5200 at f0000000/ata at 3a00";
>>>> +
>>>> + nodeoffset = fdt_path_offset (blob, nodename);
>>>> + if (nodeoffset >= 0) {
>>>> + fdt_del_node(blob, nodeoffset);
>>>> + } else
>>>> + printf("%s: cannot find %s node err:%s\n",
>>>> + __func__, nodename, fdt_strerror(nodeoffset));
>>> Incorrect multi-line parentheses:
>>>
>>> if (nodeoffset >= 0) {
>>> fdt_del_node(blob, nodeoffset);
>>> } else {
>>> printf("%s: cannot find %s node err:%s\n",
>>> __func__, nodename, fdt_strerror(nodeoffset));
>>> }
>> if (nodeoffset >= 0)
>> fdt_del_node(blob, nodeoffset);
>> else
>> printf("%s: cannot find %s node err:%s\n",
>> __func__, nodename,
>> fdt_strerror(nodeoffset));
>>
>> Should be right, or?
>
> No. IIRC, then when one of the statements is a multi-line statement, both
> statements of the if/else struct should have the parentheses.
I see only one statement in the if and the else case ...
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2009-09-14 15:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 7:14 [U-Boot] [PATCH 2/2] mucmc52, uc101: delete ata@3a00 node, if no CF card is detected Heiko Schocher
2009-09-09 8:38 ` Wolfgang Denk
2009-09-09 9:12 ` Heiko Schocher
2009-09-09 9:03 ` Wolfgang Denk
2009-09-10 5:56 ` [U-Boot] [PATCHv2 " Heiko Schocher
2009-09-14 13:07 ` Detlev Zundel
2009-09-14 15:06 ` Heiko Schocher
2009-09-14 15:06 ` [U-Boot] [PATCH v4 " Heiko Schocher
2009-09-14 15:03 ` Stefan Roese
2009-09-14 15:26 ` Heiko Schocher
2009-09-14 15:29 ` Stefan Roese
2009-09-14 15:55 ` Heiko Schocher [this message]
2009-09-14 15:44 ` Stefan Roese
2009-09-14 16:04 ` Heiko Schocher
2009-09-14 15:08 ` Stefan Roese
2009-09-14 15:36 ` Heiko Schocher
2009-09-14 15:09 ` Jerry Van Baren
2009-09-14 15:38 ` Heiko Schocher
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=4AAE6755.5060205@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.de \
/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