public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Todd Poynor <tpoynor@mvista.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Mark Lord <lkml@rtr.ca>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dsingleton@mvista.com
Subject: Re: [PATCH] Configure IDE probe delays
Date: Fri, 06 Aug 2004 13:46:19 -0700	[thread overview]
Message-ID: <4113EE1B.4030200@mvista.com> (raw)
In-Reply-To: <4113DC15.8040102@am.sony.com>

At the risk of flogging this horse after the death certificate was just 
signed, there were two threads running through the discussion and I 
wasn't sure where things stand.  One thread, as I read it, was: "Don't 
hack around the delays, let's change the probing and do it right".  The 
other thread was: "Don't mess around with IDE probing, leave that alone 
and let's do it right for SATA".

If the latter route is how things are headed then I'd still suggest 
replacing the scattered hardcoded "50" constants with a meaningful symbol.

If, on the other hand, IDE probe delays might someday become more 
complicated, such that a single symbol is not sufficient (as Alan warned 
against), then at least it would be easier to find 'em all.  And 
converting some of the calls to use a new symbol for a new class of 
delays would be quite easy.

Anyhow, not a big deal; if there's anything I can help out with to 
improve the situation then I'd be glad to do so.

-- 
Todd Poynor
MontaVista Software


  reply	other threads:[~2004-08-06 20:51 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 19:11 [PATCH] Configure IDE probe delays Todd Poynor
2004-07-30 21:36 ` Lee Revell
2004-07-30 22:35 ` Alan Cox
2004-07-31  0:12   ` Lee Revell
     [not found]     ` <200407311434.59604.vda@port.imtp.ilyichevsk.odessa.ua>
2004-07-31 18:00       ` Lee Revell
2004-08-27 17:45         ` Greg Stark
2004-08-27 17:53           ` Lee Revell
2004-08-27 18:05             ` Bartlomiej Zolnierkiewicz
2004-08-27 18:08               ` Lee Revell
2004-08-27 18:59                 ` Bartlomiej Zolnierkiewicz
2004-09-01 13:20                   ` Mark Lord
2004-09-01 14:43                     ` Jeff Garzik
2004-09-01 15:30                       ` Mark Lord
2004-09-01 15:36                       ` Mark Lord
2004-09-01 19:36                         ` Lee Revell
2004-09-01 18:42                           ` Alan Cox
2004-09-01 15:06                     ` Alan Cox
2004-09-01 19:08                       ` Lee Revell
2004-09-02 16:04                       ` Mark Lord
2004-09-01 15:40                     ` Bartlomiej Zolnierkiewicz
2004-07-31 18:06       ` Lee Revell
2004-07-31 19:35         ` Alan Cox
2004-07-31 21:35           ` Lee Revell
2004-07-31 21:44             ` Jeff Garzik
2004-07-31 22:12               ` Lee Revell
2004-08-04 17:30               ` Anthony de Boer
2004-08-05 21:39           ` Tim Bird
2004-07-31  0:54   ` Jeff Garzik
2004-08-03 17:47     ` Mark Lord
2004-08-06 15:48       ` Jeff Garzik
2004-08-06 19:29         ` Tim Bird
2004-08-06 20:46           ` Todd Poynor [this message]
2004-08-02 21:56   ` Tim Bird
2004-08-02 21:01     ` Alan Cox

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=4113EE1B.4030200@mvista.com \
    --to=tpoynor@mvista.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dsingleton@mvista.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=tim.bird@am.sony.com \
    /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