linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Norman Diamond <n0diamond@yahoo.co.jp>
Cc: Mark Lord <liml@rtr.ca>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Chuck Ebbert <cebbert@redhat.com>,
	linux-ide@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>
Subject: Re: Kernel bug crashing in HDIO_DRIVE_TASKFILE
Date: Fri, 27 Feb 2009 21:14:34 -0600	[thread overview]
Message-ID: <49A8AC1A.1000900@gmail.com> (raw)
In-Reply-To: <B2BE4BF16058416F88555755CB1823DF@DIAMOND8600>

Norman Diamond wrote:
>> Libata should be used for any new setup that doesn't have a strict legacy
>> requirement now.
> 
> 90% agreed.  However, I've read that libata will never support add-on IDE
> boards.

Huh? It already does support most or all that one is likely to see..

  reply	other threads:[~2009-02-28  3:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 11:36 Kernel bug crashing in HDIO_DRIVE_TASKFILE Norman Diamond
2009-02-24 22:10 ` Chuck Ebbert
2009-02-25 11:43   ` Norman Diamond
2009-02-25 16:24     ` Mark Lord
2009-02-25 19:35       ` Bartlomiej Zolnierkiewicz
2009-02-25 21:18         ` Norman Diamond
2009-02-25 22:43           ` Mark Lord
2009-02-26 11:56             ` Norman Diamond
2009-02-28  3:14               ` Robert Hancock [this message]
2009-03-01  0:58                 ` Norman Diamond
2009-03-01  1:16                   ` Alan Cox
2009-03-01 11:06                   ` Robert Hancock
2009-03-02  0:24                     ` Norman Diamond
2009-03-02  2:38                       ` Robert Hancock
2009-03-02 11:43                         ` Norman Diamond
2009-03-11 22:33                       ` Bartlomiej Zolnierkiewicz
2009-03-11 23:00                         ` Norman Diamond
  -- strict thread matches above, loose matches on Subject: below --
2009-03-03 11:44 Norman Diamond

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=49A8AC1A.1000900@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=bzolnier@gmail.com \
    --cc=cebbert@redhat.com \
    --cc=jens.axboe@oracle.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=n0diamond@yahoo.co.jp \
    /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).