From: Dale Farnsworth <dale@farnsworth.org>
To: Remi Machet <rmachet@slac.stanford.edu>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 2/2 v2] sysdev,mv64x60: initialization of mv64x60 ethernet, serial and I2C
Date: Mon, 21 Apr 2008 11:23:57 -0700 [thread overview]
Message-ID: <20080421182357.GB12468@farnsworth.org> (raw)
In-Reply-To: <1208799434.5789.53.camel@pcds-ts102.slac.stanford.edu>
On Mon, Apr 21, 2008 at 10:37:14AM -0700, Remi Machet wrote:
> If one of the devices of the mv64x60 init fails, the remaining
> devices are not initialized => This patch change the code to
> display an error and continue the initialization.
>
> Signed-off-by: Remi Machet (rmachet@slac.stanford.edu)
> ---
> This is the second part of the re-submission of my patch of 4/17/2008
> titled "[PATCH] sysdev,mv64x60: initialization of mv64x60 ethernet,
> serial and I2C"
>
> --- a/arch/powerpc/sysdev/mv64x60_dev.c
> +++ b/arch/powerpc/sysdev/mv64x60_dev.c
> @@ -431,9 +431,14 @@ static int __init mv64x60_device_setup(void)
> int err;
>
> id = 0;
> - for_each_compatible_node(np, "serial", "marvell,mv64360-mpsc")
> - if ((err = mv64x60_mpsc_device_setup(np, id++)))
> - goto error;
> + for_each_compatible_node(np, "serial", "marvell,mv64360-mpsc") {
> + err = mv64x60_mpsc_device_setup(np, id++);
> + if (err) {
> + printk(KERN_ERR "Failed to initialize MV64x60 " \
No need for the backslash continuation above. Also below.
> + "serial device %s: error %d.\n",
> + np->full_name, err);
> + };
You don't need the braces around the single printk statement.
> + };
No need for the semi-colon following closing brace, also below.
>
> id = 0;
> id2 = 0;
> @@ -441,38 +446,46 @@ static int __init mv64x60_device_setup(void)
> pdev = mv64x60_eth_register_shared_pdev(np, id++);
> if (IS_ERR(pdev)) {
> err = PTR_ERR(pdev);
> - goto error;
> - }
> + printk(KERN_ERR "Failed to initialize MV64x60 " \
> + "network block %s: error %d.\n",
> + np->full_name, err);
> + continue;
> + };
> for_each_child_of_node(np, np2) {
> if (!of_device_is_compatible(np2,
> "marvell,mv64360-eth"))
> continue;
> err = mv64x60_eth_device_setup(np2, id2++, pdev);
> if (err) {
> - of_node_put(np2);
> - goto error;
> + printk(KERN_ERR "Failed to initialize " \
> + "MV64x60 network device %s: " \
> + "error %d.\n",
> + np2->full_name, err);
> }
> }
> }
>
> id = 0;
> - for_each_compatible_node(np, "i2c", "marvell,mv64360-i2c")
> - if ((err = mv64x60_i2c_device_setup(np, id++)))
> - goto error;
> + for_each_compatible_node(np, "i2c", "marvell,mv64360-i2c") {
> + err = mv64x60_i2c_device_setup(np, id++);
> + if (err) {
> + printk(KERN_ERR "Failed to initialize MV64x60 I2C " \
> + "bus %s: error %d.\n",
> + np->full_name, err);
> + };
> + };
>
> /* support up to one watchdog timer */
> np = of_find_compatible_node(np, NULL, "marvell,mv64360-wdt");
> if (np) {
> if ((err = mv64x60_wdt_device_setup(np, id)))
> - goto error;
> + printk(KERN_ERR "Failed to initialize MV64x60 " \
> + "Watchdog %s: error %d.\n",
> + np->full_name, err);
> of_node_put(np);
> }
>
> return 0;
> -
> -error:
> - of_node_put(np);
> - return err;
> }
> arch_initcall(mv64x60_device_setup);
prev parent reply other threads:[~2008-04-21 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 17:37 [PATCH 2/2 v2] sysdev,mv64x60: initialization of mv64x60 ethernet, serial and I2C Remi Machet
2008-04-21 18:23 ` Dale Farnsworth [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=20080421182357.GB12468@farnsworth.org \
--to=dale@farnsworth.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=rmachet@slac.stanford.edu \
/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