From: Simon Horman <horms@verge.net.au>
To: Bernhard Walle <bwalle@suse.de>
Cc: Bernhard Walle <bernhard.walle@gmx.de>,
kexec@lists.infradead.org, vgoyal@redhat.com
Subject: Re: [PATCH 3/5] Parse /sys/firmware/memmap.
Date: Mon, 7 Jul 2008 17:06:22 +1000 [thread overview]
Message-ID: <20080707070621.GD788@verge.net.au> (raw)
In-Reply-To: <1215385571-11844-4-git-send-email-bwalle@suse.de>
On Mon, Jul 07, 2008 at 01:06:09AM +0200, Bernhard Walle wrote:
> From: Bernhard Walle <bernhard.walle@gmx.de>
>
> After the patch that provides /sys/firmware/memmap has been merged in the 'tip'
> tree by Ingo Molnar, kexec should use that interface.
>
> This patch implements architecture-independent parsing in a new file called
> firmware_memmap.c. The x86 part is ported to use that memory map for
> kexec. We don't use that memory map for building the ELF core headers,
> that was the intention for that new interface.
Hi Bernhard,
I am seeing a build problem when compiling for i386
exec/firmware_memmap.c: In function `parse_numeric_sysfs':
kexec/firmware_memmap.c:55: error: `ULLONG_MAX' undeclared (first use in
this function)
kexec/firmware_memmap.c:55: error: (Each undeclared identifier is
reported only once
kexec/firmware_memmap.c:55: error: for each function it appears in.)
kexec/firmware_memmap.c: In function `parse_memmap_entry':
kexec/firmware_memmap.c:117: error: `ULLONG_MAX' undeclared (first use
in this function)
--
Horms
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-07-07 7:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 23:06 Use /sys/firmware/memmap in kexec Bernhard Walle
2008-07-06 23:06 ` [PATCH 1/5] Remove trailing whitespace Bernhard Walle
2008-07-07 7:02 ` Simon Horman
2008-07-06 23:06 ` [PATCH 2/5] Fix compiler warning in kexec-x86.c Bernhard Walle
2008-07-07 7:03 ` Simon Horman
2008-07-06 23:06 ` [PATCH 3/5] Parse /sys/firmware/memmap Bernhard Walle
2008-07-07 7:06 ` Simon Horman [this message]
2008-07-07 14:43 ` Bernhard Walle
2008-07-07 14:43 ` [PATCH 1/3] " Bernhard Walle
2008-07-07 14:43 ` [PATCH 2/3] Remove redundancy between get_memory_ranges_proc_iomem() and get_memory_ranges_sysfs() Bernhard Walle
2008-07-09 0:41 ` Simon Horman
2008-07-09 11:10 ` Parse /sys/firmware/memmap Bernhard Walle
2008-07-09 11:11 ` [PATCH 1/3] " Bernhard Walle
2008-07-10 23:29 ` Simon Horman
2008-07-09 11:11 ` [PATCH 2/3] Remove redundancy between get_memory_ranges_proc_iomem() and get_memory_ranges_sysfs() Bernhard Walle
2008-07-09 11:11 ` [PATCH 3/3] Use get_memory_ranges() on x86-64 Bernhard Walle
2008-07-09 11:12 ` [PATCH 2/3] Remove redundancy between get_memory_ranges_proc_iomem() and get_memory_ranges_sysfs() Bernhard Walle
[not found] ` <20080710232834.GG11227@verge.net.au>
2008-07-11 15:09 ` Bernhard Walle
2008-07-07 14:43 ` [PATCH 3/3] Use get_memory_ranges() on x86-64 Bernhard Walle
2008-07-06 23:06 ` [PATCH 4/5] Remove redundancy between get_memory_ranges_proc_iomem() and get_memory_ranges_sysfs() Bernhard Walle
2008-07-06 23:06 ` [PATCH 5/5] Use get_memory_ranges() on x86-64 Bernhard Walle
-- strict thread matches above, loose matches on Subject: below --
2008-07-06 23:13 Use /sys/firmware/memmap in kexec Bernhard Walle
2008-07-06 23:13 ` [PATCH 3/5] Parse /sys/firmware/memmap Bernhard Walle
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=20080707070621.GD788@verge.net.au \
--to=horms@verge.net.au \
--cc=bernhard.walle@gmx.de \
--cc=bwalle@suse.de \
--cc=kexec@lists.infradead.org \
--cc=vgoyal@redhat.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 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).