linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] ata_timing: ensure t->cycle is always correct
Date: Sat, 28 Apr 2007 14:51:43 -0400	[thread overview]
Message-ID: <463397BF.9010406@garzik.org> (raw)
In-Reply-To: <20070423115536.38a7e43c@the-village.bc.nu>

Alan Cox wrote:
> Russell King hit a case where quantisation errors accumulated such that
> the cycle time was shorter than rather than equal to the active/recovery
> time. The code already knows how to stretch times to fit the cycle time
> but does not know about the reverse. 
> 
> Signed-off-by: Alan Cox <alan@redhat.com>

applied



      reply	other threads:[~2007-04-28 18:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 10:55 [PATCH] ata_timing: ensure t->cycle is always correct Alan Cox
2007-04-28 18:51 ` Jeff Garzik [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=463397BF.9010406@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.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).