From: Matthew McClintock <msm@freescale.com>
To: kexec@lists.infradead.org
Subject: Re: [PATCH] Fix case where phys_addr_t != unsigned long when reading proc entries
Date: Wed, 14 Jul 2010 10:39:18 -0500 [thread overview]
Message-ID: <1279121958.13098.1.camel@localhost> (raw)
In-Reply-To: <1279121556-8069-1-git-send-email-msm@freescale.com>
On Wed, 2010-07-14 at 10:32 -0500, Matthew McClintock wrote:
> On some actitectures the physical memory can be 64 bits, therefore
> the code that reads proc entries needs to take into account it could
> read either a 32 bit or 64bit value for the physical addresses.
>
These patches did not get numbered, shall I resubmit with numbered
patches?
0001-Fix-case-where-phys_addr_t-unsigned-long-when-rea.patch
0002-Update-uImage-to-support-crash-kernel-and-misc-fixes.patch
0003-Update-Elf-ppc-to-support-crash-kernel-and-misc-fixe.patch
0004-Add-support-for-ramdisk-on-ppc32-for-uImage-ppc-and.patch
0005-Add-support-for-reworking-flat-device-tree-support.patch
-M
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2010-07-14 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 15:32 [PATCH] Fix case where phys_addr_t != unsigned long when reading proc entries Matthew McClintock
2010-07-14 15:32 ` [PATCH] Update uImage to support crash kernel and misc fixes Matthew McClintock
2010-07-14 15:32 ` [PATCH] Update Elf-ppc " Matthew McClintock
2010-07-14 15:32 ` [PATCH] Add support for ramdisk on ppc32 for uImage-ppc and Elf-ppc Matthew McClintock
2010-07-14 15:32 ` [PATCH] Add support for reworking flat device tree support Matthew McClintock
2010-07-14 15:39 ` Matthew McClintock [this message]
2010-07-15 3:07 ` [PATCH] Fix case where phys_addr_t != unsigned long when reading proc entries Simon Horman
2010-07-15 4:22 ` Matthew McClintock
2010-07-15 5:47 ` Simon Horman
2010-07-14 15:49 ` [linuxppc-release] " Tabi Timur-B04825
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=1279121958.13098.1.camel@localhost \
--to=msm@freescale.com \
--cc=kexec@lists.infradead.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 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.