linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] davinci: Add MityDSP-L138/MityARM-1808 SOM support
Date: Mon, 19 Jul 2010 08:58:34 -0700	[thread overview]
Message-ID: <1279555114.5434.27.camel@Joe-Laptop.home> (raw)
In-Reply-To: <4C4454AF.4000801@criticallink.com>

On Mon, 2010-07-19 at 09:35 -0400, Michael Williamson wrote:
> +        pr_warning("%s: mmcsd0 mux setup failed:" " %d\n", __func__,ret);

Isn't this easier to read as a single string?

	pr_warning("%s: mmcsd0 mux setup failed: %d\n", __func__, ret);

Also, if you want __func__ to prefix every printk you could use:

#define pr_fmt(fmt) "%s: " fmt, __func__

and use:

	pr_warning("mmcsd0 mux setup failed: %d\n", ret);

> +    ret = da8xx_register_mmcsd0(&da850_mmc_config);
> +    if (ret)
> +        pr_warning("%s: mmcsd0 registration failed:", __func__, " %d\n", ret);

Compile tested?  Perhaps you mean:

	pr_warning("%s: mmcsd0 registration failed: %d\n", __func__, ret);

[]

> +    pr_info("EMAC = %02X:%02X:%02X:%02X:%02X:%02X\n",
> +        peripheral_config.ENETConfig.MACAddr[0],
> +        peripheral_config.ENETConfig.MACAddr[1],
> +        peripheral_config.ENETConfig.MACAddr[2],
> +        peripheral_config.ENETConfig.MACAddr[3],
> +        peripheral_config.ENETConfig.MACAddr[4],
> +        peripheral_config.ENETConfig.MACAddr[5]);

There's are extensions to printk/vsnprintf that is used for
various things like MAC and IP addresses. (see: lib/vsprintf.c)

This should be:

	pr_info("EMAC = %pM\n", peripheral_config.ENETConfig.MACAddr);

  reply	other threads:[~2010-07-19 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19 13:35 [PATCH v2] davinci: Add MityDSP-L138/MityARM-1808 SOM support Michael Williamson
2010-07-19 15:58 ` Joe Perches [this message]
2010-07-19 16:26   ` Michael Williamson
     [not found] <4C44515A.4030003@criticallink.com>
2010-07-19 14:20 ` Christophe Aeschlimann
2010-07-19 14:22 ` Christophe Aeschlimann
2010-07-19 19:36 ` Russell King - ARM Linux
2010-07-19 20:24   ` Michael Williamson

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=1279555114.5434.27.camel@Joe-Laptop.home \
    --to=joe@perches.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).