public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tupshin Harper <tupshin@tupshin.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.11-ac1
Date: Thu, 10 Mar 2005 01:06:57 -0800	[thread overview]
Message-ID: <42300E31.5030301@tupshin.com> (raw)
In-Reply-To: <1110407945.3072.272.camel@localhost.localdomain>

Alan Cox wrote:

>On Mer, 2005-03-09 at 22:22, CaT wrote:
>  
>
>>Argh! Ok. I guess I shouldn't've just bought the card based on this
>>driver then so that I could better debug my problems with my promise
>>cards. 8(
>>    
>>
>
>Its good hardware. It does lots of neat things providing you run -ac
>anyway. The raid1 performance is very good and it can do hotplug IDE
>transparently in hardware raid modes. Its a good solid little
>controller. 
>
>Alan
>
Alan...since you disagreed with the earlier characterization of what it 
would take to get into the mainline kernels, could you let us know what 
it would take in your opinion? FWIW, I'm happily using it with a -ac kernel.

-Tupshin

  reply	other threads:[~2005-03-10  9:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07 21:34 Linux 2.6.11-ac1 Alan Cox
2005-03-08  6:02 ` Clemens Schwaighofer
2005-03-08  6:49   ` Chris Wright
2005-03-08  6:52     ` Clemens Schwaighofer
2005-03-08 12:47     ` Stephen C. Tweedie
2005-03-08 12:00 ` Andre Tomt
2005-03-09  7:26 ` CaT
2005-03-09 15:51   ` Alan Cox
2005-03-10  8:03     ` Denis Vlasenko
2005-03-09 16:26   ` Bartlomiej Zolnierkiewicz
2005-03-09 16:38     ` Alan Cox
2005-03-09 16:43       ` Bartlomiej Zolnierkiewicz
2005-03-09 22:22         ` CaT
2005-03-09 22:39           ` Alan Cox
2005-03-10  9:06             ` Tupshin Harper [this message]
2005-03-10 15:01               ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2005-03-07 23:26 Indrek Kruusa

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=42300E31.5030301@tupshin.com \
    --to=tupshin@tupshin.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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