public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Winchester <kjwinchester@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Warning when compiling arch/x86/mm/init_64.c on x86_64
Date: Tue, 10 Jun 2008 20:56:37 -0300	[thread overview]
Message-ID: <484F14B5.4090204@gmail.com> (raw)
In-Reply-To: <484EED06.8060301@lwfinger.net>

Larry Finger wrote:
> Since commit 511631011d39706ac81ee5e4c9084d61e5b4fd34, entitled
> "x86: fix pointer type warning in arch/x86/mm/init_64.c:early_memtest", the 
> following warning is produced for x86_64:
> 
> arch/x86/mm/init_64.c: In function ‘early_memtest’:
> arch/x86/mm/init_64.c:520: warning: passing argument 2 of 
> ‘find_e820_area_size’ from incompatible pointer type
> 
> Before this commit, the compilation of this routine on my system was clean. I 
> use gcc version 4.2.1. Was this the warning for i386 before the patch? I 
> tried simple changes in the definition of find_e820_area_size, but only 
> managed to push the warning on to the call to bad_addr_size. At that point I 
> decided to let the experts find a proper fix. Note that the warning does no 
> harm - I just get nervous about incompatible pointer warnings as it usually 
> means that I have screwed something up.
> 

The patch was against linux-next, which seems to have changed 
find_e820_area_size() - against mainline it introduced the warning 
instead of fixing it.

-- 
Kevin Winchester


      reply	other threads:[~2008-06-10 23:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 21:07 Warning when compiling arch/x86/mm/init_64.c on x86_64 Larry Finger
2008-06-10 23:56 ` Kevin Winchester [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=484F14B5.4090204@gmail.com \
    --to=kjwinchester@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --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