From: "Craig Lyons" <craigl@promise.com>
To: <linux-kernel@vger.kernel.org>
Subject: Getting A Patch Into The Kernel
Date: Tue, 12 Jun 2001 15:34:43 -0700 [thread overview]
Message-ID: <005101c0f38f$e2000960$bd01a8c0@promise.com> (raw)
Hello,
My name is Craig Lyons and I am the marketing manager at Promise Technology.
We have a question and are hoping you can point us in the right direction.
In the 2.4 kernel there is support for some of our products (Ultra 66, Ultra
100, etc.). As you may or may not know, our Ultra family of controllers
(which are just standard IDE controllers and do not have RAID) use the same
ASIC on them as our FastTrak RAID controllers do. The 2.4 kernel will
recognize our Ultra family of controllers, but there is a problem in that a
FastTrak will not be recognized as a FastTrak, but as an Ultra.
Consequently, the array on the FastTrak is not recognized as an array, but
instead each disk is seen individually, and the users data cannot be
properly accessed. We have a patch that fixes this and are wondering if it
is possible to get this patch into the kernel, and if so, how this would be
done?
I apologize if this is the incorrect e-mail to be making this request to. If
this is not the correct address to be posting this message, any assistance
as to where it should be directed would be greatly appreciated.
Regards,
Craig
Craig Lyons
Marketing Manager
Promise Technology
1460 Koll Circle
San Jose, CA 95112
USA
Voice - 408-452-0948 ext. 241
Fax - 408-452-1534
craigl@promise.com
http:\\www.promise.com
next reply other threads:[~2001-06-12 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 22:34 Craig Lyons [this message]
2001-06-12 18:32 ` Getting A Patch Into The Kernel Rob Landley
2001-06-12 23:21 ` Robert Love
2001-06-13 0:34 ` Rik van Riel
2001-06-13 23:18 ` Alan Cox
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='005101c0f38f$e2000960$bd01a8c0@promise.com' \
--to=craigl@promise.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.