From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Loeliger <jdl@freescale.com>
Cc: "linuxppc-embedded@ozlabs.org" <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] PPC32 mem_pieces interface cleanup
Date: Tue, 28 Jun 2005 16:30:37 +1000 [thread overview]
Message-ID: <1119940238.5133.206.camel@gaston> (raw)
In-Reply-To: <1119889730.25557.19.camel@cashmere.sps.mot.com>
On Mon, 2005-06-27 at 11:28 -0500, Jon Loeliger wrote:
> Guys,
>
> As an initial step towards getting the OF Flat Dev tree
> handled in the PPC32 tree, this patch cleans up some of
> the interface parts of the very early mem_pieces manager
> and adds some PPC64-LMB-like routines as well.
>
> It has been built and booted on 85xx and pmac boards.
Please make sure you CC linuxppc-dev on such patches or they'll be
missed by me and/or paulus most of the time :)
Ben.
prev parent reply other threads:[~2005-06-28 6:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 16:28 [PATCH] PPC32 mem_pieces interface cleanup Jon Loeliger
2005-06-28 6:30 ` Benjamin Herrenschmidt [this message]
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=1119940238.5133.206.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jdl@freescale.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).