From: Simon Horman <horms@verge.net.au>
To: Matthew McClintock <msm@freescale.com>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH] Fix case where phys_addr_t != unsigned long when reading proc entries
Date: Thu, 15 Jul 2010 12:07:48 +0900 [thread overview]
Message-ID: <20100715030748.GA11508@verge.net.au> (raw)
In-Reply-To: <1279121958.13098.1.camel@localhost>
On Wed, Jul 14, 2010 at 10:39:18AM -0500, Matthew McClintock wrote:
> 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?
The list below is sufficient, but could you cc the patches to
linuxppc-dev@lists.ozlabs.org?
> 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
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2010-07-15 3:07 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 ` [PATCH] Fix case where phys_addr_t != unsigned long when reading proc entries Matthew McClintock
2010-07-15 3:07 ` Simon Horman [this message]
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=20100715030748.GA11508@verge.net.au \
--to=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=msm@freescale.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