From: Tom Rini <trini@kernel.crashing.org>
To: James Chapman <jchapman@katalix.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: PATCH: add ppc PVR register values for 7447A and 7457 CPUs
Date: Wed, 23 Feb 2005 15:25:34 -0700 [thread overview]
Message-ID: <20050223222534.GM345@smtp.west.cox.net> (raw)
In-Reply-To: <421CEC19.2010703@katalix.com>
On Wed, Feb 23, 2005 at 08:48:25PM +0000, James Chapman wrote:
> Signed-off-by: James Chapman <jchapman@katalix.com>
>
> Trivial patch to add 7447A and 7457 CPU defs.
Why? Most of the PVR definitions here can be removed (*muttering about
85xx ones being added).
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-02-23 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 20:48 PATCH: add ppc PVR register values for 7447A and 7457 CPUs James Chapman
2005-02-23 22:25 ` Tom Rini [this message]
2005-02-23 22:52 ` Kumar Gala
2005-02-24 5:16 ` Kumar Gala
2005-02-24 9:01 ` James Chapman
2005-02-24 14:18 ` Tom Rini
2005-02-24 15:50 ` James Chapman
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=20050223222534.GM345@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=jchapman@katalix.com \
--cc=linuxppc-dev@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).