linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP4: SRAM: Fix warning: format '%08lx' expects type 'long unsigned int'
Date: Thu, 28 Apr 2011 15:09:53 +0100	[thread overview]
Message-ID: <20110428140953.GD19709@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4D9993AD.3080401@ti.com>

On Mon, Apr 04, 2011 at 03:17:25PM +0530, Santosh Shilimkar wrote:
> From 4d8d4e5c99c1477a8cb04b525ff5a2d93bbdacfd Mon Sep 17 00:00:00 2001
> From: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Date: Mon, 4 Apr 2011 14:20:08 +0530
> Subject: [PATCH] OMAP: SRAM: Fix warning: format '%08lx' expects type  
> 'long unsigned int'
>
> Fix below build warning.
>
>  CC	arch/arm/plat-omap/sram.o
> 	arch/arm/plat-omap/sram.c: In function 'omap_map_sram':
> 	arch/arm/plat-omap/sram.c:224: warning: format '%08lx' expects
> 	type 'long unsigned int', but argument 2 has type 'unsigned int'
>
> While at this, convert SRAM printk(* "") to pr_*("").
>
> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> ---
>  arch/arm/plat-omap/sram.c |   12 ++++++------
>  1 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm/plat-omap/sram.c b/arch/arm/plat-omap/sram.c
> index a3f50b3..6af3d0b 100644
> --- a/arch/arm/plat-omap/sram.c
> +++ b/arch/arm/plat-omap/sram.c
> @@ -166,7 +166,7 @@ static void __init omap_detect_sram(void)
>  		else if (cpu_is_omap1611())
>  			omap_sram_size = SZ_256K;
>  		else {
> -			printk(KERN_ERR "Could not detect SRAM size\n");
> +			pr_err("Could not detect SRAM size\n");
>  			omap_sram_size = 0x4000;
>  		}
>  	}
> @@ -221,10 +221,10 @@ static void __init omap_map_sram(void)
>  	omap_sram_io_desc[0].length = ROUND_DOWN(omap_sram_size, PAGE_SIZE);
>  	iotable_init(omap_sram_io_desc, ARRAY_SIZE(omap_sram_io_desc));
>
> -	printk(KERN_INFO "SRAM: Mapped pa 0x%08lx to va 0x%08lx size: 0x%lx\n",
> -	__pfn_to_phys(omap_sram_io_desc[0].pfn),
> -	omap_sram_io_desc[0].virtual,
> -	       omap_sram_io_desc[0].length);
> +	pr_info("SRAM: Mapped pa 0x%08llx to va 0x%08lx size: 0x%lx\n",
> +		(long long) __pfn_to_phys(omap_sram_io_desc[0].pfn),
> +		omap_sram_io_desc[0].virtual,
> +		omap_sram_io_desc[0].length);
>
>  	/*
>  	 * Normally devicemaps_init() would flush caches and tlb after
> @@ -252,7 +252,7 @@ static void __init omap_map_sram(void)
>  void *omap_sram_push_address(unsigned long size)
>  {
>  	if (size > (omap_sram_ceil - (omap_sram_base + SRAM_BOOTLOADER_SZ))) {
> -		printk(KERN_ERR "Not enough space in SRAM\n");
> +		pr_err("Not enough space in SRAM\n");
>  		return NULL;
>  	}
>

This looks much better.

Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>

It looks like Tony hasn't taken it...  Tony, are you going to handle
this patch?

  parent reply	other threads:[~2011-04-28 14:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  9:04 [PATCH] OMAP4: SRAM: Fix warning: format '%08lx' expects type 'long unsigned int' Santosh Shilimkar
2011-04-04  9:12 ` Russell King - ARM Linux
2011-04-04  9:47   ` Santosh Shilimkar
2011-04-23  7:08     ` Santosh Shilimkar
2011-04-28 14:09     ` Russell King - ARM Linux [this message]
2011-05-03 10:55       ` Tony Lindgren
2011-05-31 10:23         ` Tony Lindgren

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=20110428140953.GD19709@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).