All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: craigl@promise.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Getting A Patch Into The Kernel
Date: 12 Jun 2001 19:21:50 -0400	[thread overview]
Message-ID: <992388112.5004.0.camel@phantasy> (raw)
In-Reply-To: <005101c0f38f$e2000960$bd01a8c0@promise.com>
In-Reply-To: <005101c0f38f$e2000960$bd01a8c0@promise.com>

Hi, this is the correct forum.  You can submit the patch here.  Merely
paste the patch output inline into your email, and make your subject
"[PATCH] 2.4.5 FastTrak RAID Whatever Fix" and explain in the email.

Note your code must become GPL licensed.

I would suggest making the patch against the latest kernel, 2.4.5 -- or
even better, 2.4.5-ac13 or 2.4.6-pre2.

I suggest reading linux/Documentation/SubmittingPatches for coding
standards, etc.

It is good to see manufactures supporting their products in Linux, thank
you!

-- 
Robert M. Love
rml@ufl.edu
rml@tech9.net

On 12 Jun 2001 15:34:43 -0700, Craig Lyons wrote:
> 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


  parent reply	other threads:[~2001-06-12 23:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 22:34 Getting A Patch Into The Kernel Craig Lyons
2001-06-12 18:32 ` Rob Landley
2001-06-12 23:21 ` Robert Love [this message]
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=992388112.5004.0.camel@phantasy \
    --to=rml@tech9.net \
    --cc=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.