All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Zhang Yanfei <zhangyanfei.yes@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Zhang Yanfei <zhangyanfei@cn.fujitsu.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/early_iounmap: Let the compiler enter the function name
Date: Sun, 6 Oct 2013 11:36:14 +0200	[thread overview]
Message-ID: <20131006093614.GB4535@gmail.com> (raw)
In-Reply-To: <524D56CB.9080205@gmail.com>


* Zhang Yanfei <zhangyanfei.yes@gmail.com> wrote:

> From: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
> 
> To be consistent with early_ioremap which had a change in
> commit 4f4319a ("x86/ioremap: Correct function name output"),
> let the complier enter the function name too.
> 
> Signed-off-by: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
> ---
>  arch/x86/mm/ioremap.c |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/x86/mm/ioremap.c b/arch/x86/mm/ioremap.c
> index 799580c..577bd8e 100644
> --- a/arch/x86/mm/ioremap.c
> +++ b/arch/x86/mm/ioremap.c
> @@ -585,21 +585,21 @@ void __init early_iounmap(void __iomem *addr, unsigned long size)
>  	}
>  
>  	if (slot < 0) {
> -		printk(KERN_INFO "early_iounmap(%p, %08lx) not found slot\n",
> +		printk(KERN_INFO "%s(%p, %08lx) not found slot\n", __func__,

Would be nice to fix the spelling here as well then.

>  			 addr, size);
>  		WARN_ON(1);
>  		return;
>  	}
>  
>  	if (prev_size[slot] != size) {
> -		printk(KERN_INFO "early_iounmap(%p, %08lx) [%d] size not consistent %08lx\n",
> -			 addr, size, slot, prev_size[slot]);
> +		printk(KERN_INFO "%s(%p, %08lx) [%d] size not consistent %08lx\n",
> +			 __func__, addr, size, slot, prev_size[slot]);

and here too, i.e. write:

	slot [%d] size [%08lx] not consistent with previous size [%08lx]

(Note that size can be duplicated there for completeness - even though 
it's included in the early_iounmap() printout already.)

>  	if (early_ioremap_debug) {
> -		printk(KERN_INFO "early_iounmap(%p, %08lx) [%d]\n", addr,
> +		printk(KERN_INFO "%s(%p, %08lx) [%d]\n", __func__, addr,
>  		       size, slot);
>  		dump_stack();


I'd also stick that into a debug_print() helper define that prints the 
standard bits, leaving only the important bits at actual call sites:

		debug_print("size [%08lx] not consistent with previous size [%08lx]\n
		debug_print("call\n", addr, size, slot);

Thanks,

	Ingo

      reply	other threads:[~2013-10-06  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03 11:36 [PATCH] x86/early_iounmap: Let the compiler enter the function name Zhang Yanfei
2013-10-06  9:36 ` Ingo Molnar [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=20131006093614.GB4535@gmail.com \
    --to=mingo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=zhangyanfei.yes@gmail.com \
    --cc=zhangyanfei@cn.fujitsu.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.