From: Kumar Gala <kumar.gala@freescale.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: <hpa@zytor.com>, "Olaf Hering" <olh@suse.de>,
<linux-kernel@vger.kernel.org>, <torvalds@osdl.org>,
<linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] raid6: altivec support
Date: Mon, 17 Jan 2005 08:58:17 -0600 [thread overview]
Message-ID: <38A2A735-6898-11D9-AF22-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <1105956993.26551.327.camel@hades.cambridge.redhat.com>
[snip]
> This makes it compile on PPC, but highlights the difference between
> 'cur_cpu_spec' on ppc32 and ppc64. Why is 'cur_cpu_spec' an array on
> ppc32? Isn't 'cur' supposed to imply 'current'?
I can only guess to handle an SMP case with two different revs of the
same processor that might have slightly different errata.
- kumar
next prev parent reply other threads:[~2005-01-17 14:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200501082324.j08NOIva030415@hera.kernel.org>
2005-01-09 15:13 ` [PATCH] raid6: altivec support Olaf Hering
2005-01-17 10:16 ` David Woodhouse
2005-01-17 14:58 ` Kumar Gala [this message]
2005-01-19 4:11 ` Benjamin Herrenschmidt
2005-01-19 7:43 ` David Woodhouse
2005-01-19 9:41 ` Paul Mackerras
2005-01-20 17:55 ` Tom Rini
2005-01-19 14:45 ` Kumar Gala
2005-01-19 14:48 ` David Woodhouse
2005-01-19 14:54 ` Kumar Gala
2005-01-19 15:08 ` Geert Uytterhoeven
2005-01-19 15:15 ` Kumar Gala
2005-01-19 15:27 ` Geert Uytterhoeven
2005-01-19 23:25 ` Benjamin Herrenschmidt
2005-01-20 7:40 ` [Lists-linux-kernel-news] " Jon Masters
2005-01-19 18:07 ` Jon Masters
2005-01-19 23:22 ` Benjamin Herrenschmidt
2005-01-23 11:17 ` Sven Luther
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=38A2A735-6898-11D9-AF22-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olh@suse.de \
--cc=torvalds@osdl.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).