From: Tejun Heo <tj@kernel.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.32-rc3] fix pcpu_embed_first_chunk() compile warnings
Date: Mon, 12 Oct 2009 17:01:28 +0900 [thread overview]
Message-ID: <4AD2E258.9090706@kernel.org> (raw)
In-Reply-To: <19151.3066.304514.621378@pilspetsen.it.uu.se>
Mikael Pettersson wrote:
> Compiling 2.6.32-rc3 on i686 I get the following new warnings:
>
> mm/percpu.c: In function 'pcpu_embed_first_chunk':
> mm/percpu.c:1873: warning: comparison of distinct pointer types lacks a cast
> mm/percpu.c:1879: warning: format '%lx' expects type 'long unsigned int', but argument 2 has type 'size_t'
>
> They are caused by 6ea529a2037ce662fc6bfa572b46d47407d08805
> "make embedding first chunk allocator check vmalloc space size".
>
> The first warning is because max() is applied to one operand of
> type 'size_t' and another of type 'unsigned long'. Fix: cast the
> second one to 'size_t'.
>
> For the second warning: always use '%z' to format 'size_t' operands.
>
> Signed-off-by: Mikael Pettersson <mikpe@it.uu.se>
For some reason, I've been thinking this was linux-next specific and
committed about the same patch there, commit 3cbeae2f, a while ago.
The only difference was use of max_t() instead of size_t cast. I
think max_t() is cleaner there and will cherry pick the patch from
linux-next.
Thanks.
--
tejun
prev parent reply other threads:[~2009-10-12 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 10:10 [PATCH 2.6.32-rc3] fix pcpu_embed_first_chunk() compile warnings Mikael Pettersson
2009-10-12 8:01 ` Tejun Heo [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=4AD2E258.9090706@kernel.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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