From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "H. Peter Anvin" <hpa@kernel.org>
Cc: Bernhard Walle <bwalle@suse.de>,
x86@kernel.org, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Always use 64 bit addresses for the firmware memory map
Date: Wed, 12 Nov 2008 16:32:14 -0800 [thread overview]
Message-ID: <491B758E.5090902@goop.org> (raw)
In-Reply-To: <491B681B.6040405@kernel.org>
H. Peter Anvin wrote:
> Jeremy Fitzhardinge wrote:
>
>> resource_size_t should always be 64-bit on PAE now.
>>
>>
>
> Yes, but this would affect non-PAE kernels too.
>
Yeah, I overlooked the comment about non-PAE. Should we just make
resource_size_t 64 bits all the time? Or ignore inaccessible resources?
J
next prev parent reply other threads:[~2008-11-13 0:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 19:44 [PATCH] Always use 64 bit addresses for the firmware memory map Bernhard Walle
2008-11-12 19:59 ` H. Peter Anvin
2008-11-12 21:11 ` Bernhard Walle
2008-11-12 23:35 ` H. Peter Anvin
2008-11-13 8:04 ` Bernhard Walle
2008-11-12 20:16 ` Jeremy Fitzhardinge
2008-11-12 23:34 ` H. Peter Anvin
2008-11-13 0:32 ` Jeremy Fitzhardinge [this message]
2008-11-13 1:16 ` H. Peter Anvin
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=491B758E.5090902@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=bwalle@suse.de \
--cc=hpa@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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