mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, gcosta@redhat.com
Subject: Re: [PATCH] Use correct format when printing long unsigned int in arch/x86/kernel/setup.c
Date: Mon, 5 May 2008 15:58:59 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0805051558001.25277@shark.he.net> (raw)
In-Reply-To: <alpine.LNX.1.00.0805060039100.27779@dragon.funnycrock.com>

On Tue, 6 May 2008, Jesper Juhl wrote:

> From: Jesper Juhl <jesper.juhl@gmail.com>
> 
> 
> Use correct format when printing long unsigned int in arch/x86/kernel/setup.c

Ugh, thanks.  Looks like I mucked that one up somehow.
I'll have to check my logs when I get back home.

> This patch gets rid of this compiler warning:
>   arch/x86/kernel/setup.c: In function 'setup_per_cpu_areas':
>   arch/x86/kernel/setup.c:99: warning: format '%zd' expects type 'signed size_t', but argument 2 has type 'long unsigned int'
> 
> 
> Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
> ---
> 
>  setup.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
> index cc6f5eb..c0c68c1 100644
> --- a/arch/x86/kernel/setup.c
> +++ b/arch/x86/kernel/setup.c
> @@ -95,7 +95,7 @@ void __init setup_per_cpu_areas(void)
>  
>  	/* Copy section for each CPU (we discard the original) */
>  	size = PERCPU_ENOUGH_ROOM;
> -	printk(KERN_INFO "PERCPU: Allocating %zd bytes of per cpu data\n",
> +	printk(KERN_INFO "PERCPU: Allocating %lu bytes of per cpu data\n",
>  			  size);
>  
>  	for_each_possible_cpu(i) {
> 
> 

-- 
~Randy

  reply	other threads:[~2008-05-05 23:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05 22:41 Jesper Juhl
2008-05-05 22:58 ` Randy.Dunlap [this message]
2008-05-06 12:38 ` Ingo Molnar

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=Pine.LNX.4.64.0805051558001.25277@shark.he.net \
    --to=rdunlap@xenotime.net \
    --cc=gcosta@redhat.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®