linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Bob Stewart <bob@evoria.net>
Cc: Mark Lord <liml@rtr.ca>, linux-ide@vger.kernel.org
Subject: Re: sata_inic162x driver for 2.6.19 timeouts etc
Date: Fri, 16 Mar 2007 15:00:55 +0900	[thread overview]
Message-ID: <45FA3297.5000105@gmail.com> (raw)
In-Reply-To: <20070316055335.51776.qmail@web811.biz.mail.mud.yahoo.com>

Bob Stewart wrote:
> BTW, did you want me to load a 2.4 kernel to test the sunix driver, or did you
> have something else in mind?  I wasn't quite clear on what I was agreeing
> to.  :)  I'm OK either way.  I've got a spare PATA drive to put the 2.4 kernel
> on if necessary, and can test with the new WD800 on the INIC162x.  I've also
> got a 200GB drive that I can do read testing with if it comes to an LBA48
> issue.

It would be great if you can test the sunix driver on 2.4 kernel for
both LBA28 and 48 cases.  I know it's a hassle and would really
appreciate it.

> (Steelhead are a species of rainbow trout.)

Man, I love trouts.  Wish I were there.  :-)

-- 
tejun

  reply	other threads:[~2007-03-16  6:01 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02  6:29 [PATCH] libata: add 150ms between completion of hardreset and status checking Tejun Heo
2007-02-03 22:07 ` Bob Stewart
2007-02-04  2:36   ` Tejun Heo
2007-02-04  2:46     ` sata_inic162x driver for 2.6.19 timeouts etc Bob Stewart
2007-02-05 17:29       ` Mark Lord
2007-02-05 21:55         ` Bob Stewart
2007-02-06 14:42           ` Mark Lord
2007-03-15 17:40           ` Tejun Heo
2007-03-15 18:20             ` Bob Stewart
2007-03-16  5:17               ` Tejun Heo
2007-03-16  5:53                 ` Bob Stewart
2007-03-16  6:00                   ` Tejun Heo [this message]
2007-03-16  6:02                     ` Bob Stewart
2007-03-24  6:48                       ` Bob Stewart
2007-03-24  7:38                         ` Tejun Heo
2007-03-24  9:59                           ` Bob Stewart
2007-03-27  4:57                           ` Jeff Garzik
2007-03-27  5:19                             ` Bob Stewart
2007-03-27 14:23                             ` Mark Lord
2007-03-27 16:24                               ` Alan Cox
2007-03-28  1:20                           ` Bob Stewart
2007-03-28  5:21                             ` Bob Stewart
2008-08-24 23:50                           ` Old Thread: " Bob Stewart
2008-08-25  8:39                             ` Tejun Heo
2008-08-25 14:39                               ` Bob Stewart
2007-03-15 19:16             ` Alan Cox
2007-03-15 20:16               ` Jeff Garzik
2007-03-16  5:23                 ` Tejun Heo
2007-03-16 12:23                   ` Mark Lord
2007-03-16 14:55                     ` Alan Cox
2007-03-16 15:21                   ` Jeff Garzik
2007-03-17  2:09                     ` Tejun Heo
2007-03-16 15:23                   ` Jeff Garzik
2007-03-15 20:16             ` Jeff Garzik
2007-03-15 20:43             ` Bob Stewart
2007-03-16  5:13               ` Tejun Heo
2007-02-07  0:43 ` [PATCH] libata: add 150ms between completion of hardreset and status checking Jeff Garzik

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=45FA3297.5000105@gmail.com \
    --to=htejun@gmail.com \
    --cc=bob@evoria.net \
    --cc=liml@rtr.ca \
    --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).