All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Kuo <rkuo@codeaurora.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-hexagon@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] hexagon: fix printk format warning in setup.c
Date: Tue, 15 May 2018 14:03:26 -0500	[thread overview]
Message-ID: <20180515190326.GC22553@codeaurora.org> (raw)
In-Reply-To: <adce8db5-4b01-dc10-7fbb-6a64e0787eb5@infradead.org>

On Sat, May 12, 2018 at 06:48:49PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
> 
> Fix printk format warning in hexagon/kernel/setup.c:
> 
> ../arch/hexagon/kernel/setup.c: In function 'setup_arch':
> ../arch/hexagon/kernel/setup.c:69:2: warning: format '%x' expects argument of type 'unsigned int', but argument 2 has type 'long unsigned int' [-Wformat]
> 
> where:
> extern unsigned long	__phys_offset;
> #define PHYS_OFFSET	__phys_offset
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Richard Kuo <rkuo@codeaurora.org>
> Cc: linux-hexagon@vger.kernel.org
> ---
>  arch/hexagon/kernel/setup.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- linux-next-20180510.orig/arch/hexagon/kernel/setup.c
> +++ linux-next-20180510/arch/hexagon/kernel/setup.c
> @@ -66,7 +66,7 @@ void __init setup_arch(char **cmdline_p)
>  	 */
>  	__vmsetvec(_K_VM_event_vector);
>  
> -	printk(KERN_INFO "PHYS_OFFSET=0x%08x\n", PHYS_OFFSET);
> +	printk(KERN_INFO "PHYS_OFFSET=0x%08lx\n", PHYS_OFFSET);
>  
>  	/*
>  	 * Simulator has a few differences from the hardware.
> 
> 


Acked-by: Richard Kuo <rkuo@codeaurora.org>

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, 
a Linux Foundation Collaborative Project

      reply	other threads:[~2018-05-15 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13  1:48 [PATCH] hexagon: fix printk format warning in setup.c Randy Dunlap
2018-05-15 19:03 ` Richard Kuo [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=20180515190326.GC22553@codeaurora.org \
    --to=rkuo@codeaurora.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@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 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.