From: Iain McClatchie <iain@TrueCircuits.com>
To: linux-kernel@vger.kernel.org, andre@linux-ide.org
Subject: Promise Ultra ATA 133 TX2 support for the 2.2 kernel series
Date: Fri, 21 Dec 2001 01:08:08 -0800 [thread overview]
Message-ID: <3C22FBF8.62C7B4E3@TrueCircuits.com> (raw)
Andre,
Is there any chance you will backport the Promise ATA/133
patch to the 2.2 kernel series? If not, is anyone you
know of working on a backport?
I've got a pair of 160GB Maxtors I'd like to get working
soon, perhaps without rolling the office forward to the 2.4
kernel... :) I guess my alternative to finding a 2.2 patch
somewhere is just using the first 137 GB of the drives, and
extending the partition and ext2 filesystem later when we
finally upgrade our kernels.
-Iain McClatchie iain@truecircuits.com
Chief Architect 650-691-7604 voice
True Circuits, Inc. 650-691-7606 FAX
650-703-2095 cell
next reply other threads:[~2001-12-21 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-21 9:08 Iain McClatchie [this message]
2001-12-21 12:06 ` Promise Ultra ATA 133 TX2 support for the 2.2 kernel series Davidovac Zoran
2001-12-21 13:34 ` Peter Svensson
2001-12-21 14:07 ` Davidovac Zoran
2001-12-21 15:17 ` Peter Svensson
2001-12-21 21:03 ` Iain McClatchie
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=3C22FBF8.62C7B4E3@TrueCircuits.com \
--to=iain@truecircuits.com \
--cc=andre@linux-ide.org \
--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