From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Paul Mackerras <paulus@samba.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH 2.6] LongTrail W83C553 IDE
Date: Mon, 19 Jan 2004 10:28:05 +1100 [thread overview]
Message-ID: <1074468485.814.35.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.58.0401181317170.653@callisto>
On Sun, 2004-01-18 at 23:22, Geert Uytterhoeven wrote:
> The patch below enables the W83C553 IDE interface on the CHRP LongTrail.
> It's a straight forward port of the W83C553 fixup code for LongTrail and Briq
> in 2.4.x. It was tested on LongTrail only, using a ST340810ACE hard drive.
> Briq support may need additional changes.
>
> The patch is relative to 2.6.0 in the linuxppc-2.5 tree on December 22.
> Please apply, thanks!
I will take care of it along with the briq stuff, thanks.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-01-18 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 12:22 [PATCH 2.6] LongTrail W83C553 IDE Geert Uytterhoeven
2004-01-18 21:24 ` Paul Mackerras
2004-01-18 21:38 ` Geert Uytterhoeven
2004-01-18 23:28 ` 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=1074468485.814.35.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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).