Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Rodolfo Giometti <giometti@linux.it>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] 3/7 AU1100 MMC support
Date: Thu, 10 Aug 2006 17:17:47 +0400	[thread overview]
Message-ID: <44DB31FB.8010806@ru.mvista.com> (raw)
In-Reply-To: <20060809210927.GD13145@enneenne.com>

Hello.

Rodolfo Giometti wrote:

> Kernel messages fixup.

    I guess the MMC patches should go to the appropriate maintainer, Russel 
King <rmk+mmc@arm.linux.org.uk>.

> Signed-off-by: Rodolfo Giometti <giometti@linux.it>

> ------------------------------------------------------------------------
> 
> diff --git a/drivers/mmc/au1xmmc.c b/drivers/mmc/au1xmmc.c
> index 6084bb8..560d6e3 100644
> --- a/drivers/mmc/au1xmmc.c
> +++ b/drivers/mmc/au1xmmc.c
> @@ -54,13 +54,16 @@ #include "au1xmmc.h"
>  
>  #define DRIVER_NAME "au1xxx-mmc"
>  
> -/* Set this to enable special debugging macros */
> -
> -#ifdef DEBUG
> -#define DBG(fmt, idx, args...) printk("au1xx(%d): DEBUG: " fmt, idx, ##args)
> +#ifdef CONFIG_MMC_DEBUG
> +#define dbg(fmt, idx, args...) printk(KERN_DEBUG "%s(%d): DEBUG: " \
> +					fmt, DRIVER_NAME, idx, ##args)

    Could also use pr_debug() here. If DEBUG is #defined, it'll print what you 
need, if not then no.

>  #else
> -#define DBG(fmt, idx, args...)
> +#define dbg(fmt, idx, args...)
>  #endif
> +#define err(fmt, idx, args...) printk(KERN_DEBUG "%s(%d): ERROR: " \
> +					fmt, DRIVER_NAME, idx, ##args)

    Are you sure KERN_DEBUG fits best for error messages, not KERN_ERR?

> +#define info(fmt, idx, args...) printk(KERN_INFO "%s(%d): " \
> +					fmt, DRIVER_NAME, idx, ##args)

    Could use pr_info() there...

WBR, Sergei

  reply	other threads:[~2006-08-10 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09 21:09 [PATCH] 3/7 AU1100 MMC support Rodolfo Giometti
2006-08-10 13:17 ` Sergei Shtylyov [this message]
2006-08-10 13:31   ` Rodolfo Giometti

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=44DB31FB.8010806@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=giometti@linux.it \
    --cc=linux-mips@linux-mips.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