From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: S5PC210/S5PC110: VMALLOC_END should be unsigned long
Date: Sat, 21 Aug 2010 09:07:45 +0900 [thread overview]
Message-ID: <001401cb40c4$e4643050$ad2c90f0$%kim@samsung.com> (raw)
In-Reply-To: <20100819011951.GA29229@july>
Kyungmin Park wrote:
>
> From: Kyungmin Park <kyungmin.park@samsung.com>
>
> Silences following build warning:
>
> arch/arm/mm/init.c: In function 'mem_init':
> arch/arm/mm/init.c:644: warning: format '%08lx' expects type 'long
> unsigned int', but argument 12 has type 'unsigned int'
>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
>
> diff --git a/arch/arm/mach-s5pv210/include/mach/vmalloc.h b/arch/arm/mach-
> s5pv210/include/mach/vmalloc.h
> index 58f515e..5b4c69b 100644
> --- a/arch/arm/mach-s5pv210/include/mach/vmalloc.h
> +++ b/arch/arm/mach-s5pv210/include/mach/vmalloc.h
> @@ -17,6 +17,6 @@
> #ifndef __ASM_ARCH_VMALLOC_H
> #define __ASM_ARCH_VMALLOC_H __FILE__
>
> -#define VMALLOC_END (0xE0000000)
> +#define VMALLOC_END (0xE0000000UL)
>
> #endif /* __ASM_ARCH_VMALLOC_H */
> diff --git a/arch/arm/mach-s5pv310/include/mach/vmalloc.h b/arch/arm/mach-
> s5pv310/include/mach/vmalloc.h
> index 3f565eb..5bf4345 100644
> --- a/arch/arm/mach-s5pv310/include/mach/vmalloc.h
> +++ b/arch/arm/mach-s5pv310/include/mach/vmalloc.h
> @@ -17,6 +17,6 @@
> #ifndef __ASM_ARCH_VMALLOC_H
> #define __ASM_ARCH_VMALLOC_H __FILE__
>
> -#define VMALLOC_END (0xF0000000)
> +#define VMALLOC_END (0xF0000000UL)
>
> #endif /* __ASM_ARCH_VMALLOC_H */
--
Ok..will apply.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2010-08-21 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 1:19 [PATCH] ARM: S5PC210/S5PC110: VMALLOC_END should be unsigned long Kyungmin Park
2010-08-21 0:07 ` Kukjin Kim [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='001401cb40c4$e4643050$ad2c90f0$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--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).