mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: jack@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] udf : enable error print in udf_read_tagged().
Date: Sun, 02 Oct 2011 22:39:25 -0700	[thread overview]
Message-ID: <1317620365.1804.7.camel@Joe-Laptop> (raw)
In-Reply-To: <1317617737-22035-1-git-send-email-linkinjeon@gmail.com>

On Mon, 2011-10-03 at 13:55 +0900, Namjae Jeon wrote:
> While reading metadata, if a problem occurs,
> Print out only one of the five case.(It also does not show a checksum properly.)
> Because currently it have been disable by undef udf_debug.
> If there is a problem with scratched disc or loader, the user needs to know which error happened.
> And I use pr_fmt instead of printk by joe's suggestion. I try to modify totally it to pr_fmt also.
[]
> diff --git a/fs/udf/udfdecl.h b/fs/udf/udfdecl.h
[]
> @@ -21,7 +23,7 @@
>  #ifdef UDFFS_DEBUG
>  #define udf_debug(f, a...) \
>  do { \
> -	printk(KERN_DEBUG "UDF-fs DEBUG %s:%d:%s: ", \
> +	pr_debug("DEBUG %s:%d:%s: ", \
>  		__FILE__, __LINE__, __func__); \
>  	printk(f, ##a); \

This isn't the same.

You should probably just use

#define udf_debug(fmt, ...)						\
	pr_debug("DEBUG %s:%d:%s: " fmt,				\
		 __FILE__, __LINE__, __func__, __VA_ARGS__)

or maybe let dynamic_debug add
__FILE__, __LINE__ and __func__
via the appropriate controls,
so this might be appropriate.

#define udf_debug(fmt, ...)						\
	pr_debug("DEBUG " fmt, __VA_ARGS__)



  reply	other threads:[~2011-10-03  5:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03  4:55 Namjae Jeon
2011-10-03  5:39 ` Joe Perches [this message]
2011-10-03  7:20   ` NamJae Jeon

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=1317620365.1804.7.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=jack@suse.cz \
    --cc=linkinjeon@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®