From: Mark Lord <liml@rtr.ca>
To: Matt Darcy <kernel-lists@projecthugo.co.uk>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: sata_mv Driver Problems Summery.
Date: Thu, 19 Jan 2006 12:10:54 -0500 [thread overview]
Message-ID: <43CFC81E.2080408@rtr.ca> (raw)
In-Reply-To: <43CF697B.6040309@projecthugo.co.uk>
Matt Darcy wrote:
> All,
>
> I/others have posted quite a few posts with regard to the sata_mv
> experimental driver included in the <2.6.15 kernels.
>
> I thought a breif summery and update of my personal experiences may
> benifit others contributing their own information and help keep a record
> of where things are up to.
...
Thanks. I may be taking on maintenance / extension of sata_mv in the
near future, and information like this is helpful.
Cheers
Mark
prev parent reply other threads:[~2006-01-19 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 10:27 sata_mv Driver Problems Summery Matt Darcy
2006-01-19 13:12 ` Bartlomiej Zolnierkiewicz
2006-01-19 13:33 ` Matt Darcy
2006-01-19 17:10 ` Mark Lord [this message]
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=43CFC81E.2080408@rtr.ca \
--to=liml@rtr.ca \
--cc=kernel-lists@projecthugo.co.uk \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).