From: Lee Revell <rlrevell@joe-job.com>
To: Dax Kelson <dax@gurulabs.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: ETA for Areca RAID driver (arcmsr) in mainline?
Date: Thu, 22 Dec 2005 02:04:24 -0500 [thread overview]
Message-ID: <1135235065.439.25.camel@mindpipe> (raw)
In-Reply-To: <1135232812.4122.20.camel@mentorng.gurulabs.com>
On Wed, 2005-12-21 at 23:26 -0700, Dax Kelson wrote:
> On Thu, 2005-12-22 at 00:34 -0500, Lee Revell wrote:
> > On Wed, 2005-12-21 at 22:20 -0700, Dax Kelson wrote:
> > > I just got a shiny new (for me at least, the card has been out for
> > > months) Areca RAID card.
> > >
> > > The driver (arcmsr) is in the -mm kernel, but hasn't yet made it to the
> > > mainline kernel. I'm curious what remains to be done before this can
> > > happen?
> >
> > Well, often all that's needed are some user reports that the driver
> > works for them.
> >
> > Does it?
>
> According to google searches, yes.
>
> At one time there was an issue raised about stack consumption, but that
> appears fixed??
I meant, does it work for *you*?
Lee
next prev parent reply other threads:[~2005-12-22 7:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 5:20 ETA for Areca RAID driver (arcmsr) in mainline? Dax Kelson
2005-12-22 5:34 ` Lee Revell
2005-12-22 6:26 ` Dax Kelson
2005-12-22 7:04 ` Lee Revell [this message]
2005-12-22 7:24 ` Dax Kelson
2005-12-22 8:17 ` Oliver Neukum
2005-12-22 8:20 ` Arjan van de Ven
2005-12-22 13:24 ` Andrew Morton
2005-12-22 19:31 ` Dax Kelson
2005-12-30 19:32 ` Randy.Dunlap
2005-12-31 5:21 ` [PATCH 2/2] Areca RAID driver (arcmsr) cleanups Randy.Dunlap
2006-01-02 17:04 ` Matthew Wilcox
2006-01-04 9:18 ` ETA for Areca RAID driver (arcmsr) in mainline? Andrew Morton
2006-01-07 5:17 ` [PATCH] Areca RAID driver (arcmsr) cleanups Randy.Dunlap
2005-12-22 6:43 ` ETA for Areca RAID driver (arcmsr) in mainline? Adrian Bunk
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=1135235065.439.25.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=dax@gurulabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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.