From: Val Henson <val@nmt.edu>
To: Cort Dougan <cort@fsmlabs.com>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Endian-ness bugs in yellowfin.c
Date: Fri, 14 Sep 2001 14:20:03 -0600 [thread overview]
Message-ID: <20010914142002.A7477@boardwalk> (raw)
In-Reply-To: <20010913195141.B799@boardwalk> <Pine.LNX.3.96.1010914014755.8683B-100000@mandrakesoft.mandrakesoft.com> <20010914125054.A23502@ftsoj.fsmlabs.com>
In-Reply-To: <20010914125054.A23502@ftsoj.fsmlabs.com>; from cort@fsmlabs.com on Fri, Sep 14, 2001 at 12:50:54PM -0600
(Removed Donald Becker from CC list since his mail server is timing out.)
On Fri, Sep 14, 2001 at 12:50:54PM -0600, Cort Dougan wrote:
> Only the PPC-based gemini board uses that driver (ncr885e) and Val is the
> maintainer of that board. These patches that she sent fix yellowfin.c for
> the ncr885e chip on the big-endian PPC. I just pointed at the junk pile,
> Val is actually doing the work to put the ncr885e drivers there.
Yep, exactly. Here's the revised patch. It lists the yellowfin
driver once in Config.in, removes the ncr885e driver, and changes the
#ifdef __powerpc__ to #ifdef __BIG_ENDIAN.
Unfortunately, the patch is now 56K. It's available for download
here:
http://www.nmt.edu/~val/patches/yellowfinpatch
-VAL
prev parent reply other threads:[~2001-09-14 20:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 1:51 [PATCH] Endian-ness bugs in yellowfin.c Val Henson
2001-09-14 2:39 ` Tom Rini
2001-09-14 2:55 ` Val Henson
2001-09-14 3:02 ` Tom Rini
2001-09-14 5:01 ` Matthew Dharm
2001-09-14 6:12 ` Val Henson
2001-09-14 9:12 ` Alan Cox
2001-09-14 6:15 ` Val Henson
2001-09-14 6:47 ` Jeff Garzik
2001-09-14 8:07 ` Kai Henningsen
2001-09-14 20:20 ` Val Henson
2001-09-14 6:49 ` Jeff Garzik
2001-09-14 18:50 ` Cort Dougan
2001-09-14 20:20 ` Val Henson [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=20010914142002.A7477@boardwalk \
--to=val@nmt.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cort@fsmlabs.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.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