From: Sander <sander@humilis.net>
To: Mark Lord <liml@rtr.ca>
Cc: Jeff Garzik <jgarzik@pobox.com>,
sander@humilis.net, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
lkml@rtr.ca
Subject: Re: Some sata_mv error messages
Date: Tue, 21 Mar 2006 08:28:59 +0100 [thread overview]
Message-ID: <20060321072859.GB4089@favonius> (raw)
In-Reply-To: <441F8599.7080703@rtr.ca>
Mark Lord wrote (ao):
> Jeff Garzik wrote:
> >For now, the goal is a system that doesn't crash and doesn't corrupt
> >data. If its occasionally slow or spits out a few errors, but
> >otherwise still works, that's pretty darned good :)
>
> I'm currently working with the original authors of sata_mv, and have
> taken over maintenance of it for now. It should progress from "highly
> experimental" to "production quality" over the next month or so.
Thanks a lot :-)
> The (mucho) updated driver I'm using here now is already much improved
> in many ways. At some point, I'll break it out into patches for Jeff.
>
> But there's one MAJOR bugfix patch that I'll release here shortly, to
> go with the interrupt handler fix already posted.
I've actually a patched kernel ready to test your patch. Only need to
boot the server, so will do that this afternoon and report back.
Sander
--
Humilis IT Services and Solutions
http://www.humilis.net
next prev parent reply other threads:[~2006-03-21 7:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060318044056.350a2931.akpm@osdl.org>
2006-03-18 15:10 ` sata_mv success on 2.6.16-rc6-mm2 (was: Re: 2.6.16-rc6-mm2) Sander
2006-03-18 19:57 ` Andrew Morton
2006-03-20 13:33 ` Some sata_mv error messages " Sander
2006-03-21 1:02 ` Some sata_mv error messages Jeff Garzik
2006-03-21 2:25 ` Dave Jones
2006-03-21 2:35 ` Jeff Garzik
2006-03-21 16:06 ` Peter Jones
2006-03-21 4:48 ` Mark Lord
2006-03-21 7:28 ` Sander [this message]
2006-03-21 19:33 ` Denis Leroy
2006-03-21 19:37 ` Jeff Garzik
2006-03-21 19:42 ` Mark Lord
2006-03-21 7:26 ` Sander
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=20060321072859.GB4089@favonius \
--to=sander@humilis.net \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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;
as well as URLs for NNTP newsgroup(s).