From: Ingo Molnar <mingo@kernel.org>
To: ard.biesheuvel@linaro.org, qiuxishi@huawei.com,
matt.fleming@intel.com, hpa@zytor.com, tglx@linutronix.de,
tony.luck@intel.com, kamezawa.hiroyu@jp.fujitsu.com,
izumi.taku@jp.fujitsu.com, linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:core/efi] efi: Add "efi_fake_mem" boot option
Date: Wed, 21 Oct 2015 13:08:07 +0200 [thread overview]
Message-ID: <20151021110807.GA17463@gmail.com> (raw)
In-Reply-To: <tip-0f96a99dab366333439e110d6ad253bc7c557c09@git.kernel.org>
* tip-bot for Taku Izumi <tipbot@zytor.com> wrote:
> Commit-ID: 0f96a99dab366333439e110d6ad253bc7c557c09
> Gitweb: http://git.kernel.org/tip/0f96a99dab366333439e110d6ad253bc7c557c09
> Author: Taku Izumi <izumi.taku@jp.fujitsu.com>
> AuthorDate: Wed, 30 Sep 2015 23:01:56 +0900
> Committer: Matt Fleming <matt.fleming@intel.com>
> CommitDate: Mon, 12 Oct 2015 14:20:09 +0100
>
> efi: Add "efi_fake_mem" boot option
So this commit started generating the following new build warning on x86 32-bit
allyesconfig and allmodconfig builds:
drivers/firmware/efi/fake_mem.c:186:20: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
Which comes from:
u64 new_memmap_phy;
...
memmap.phys_map = (void *)new_memmap_phy;
While efi_memory_map has a 32-bit pointer:
struct efi_memory_map {
void *phys_map;
void *map;
void *map_end;
int nr_map;
unsigned long desc_version;
unsigned long desc_size;
};
Thanks,
Ingo
parent reply other threads:[~2015-10-21 11:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tip-0f96a99dab366333439e110d6ad253bc7c557c09@git.kernel.org>]
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=20151021110807.GA17463@gmail.com \
--to=mingo@kernel.org \
--cc=ard.biesheuvel@linaro.org \
--cc=hpa@zytor.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=qiuxishi@huawei.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
/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.