linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: htejun@gmail.com, akpm@osdl.org, linux-ide@vger.kernel.org
Subject: Re: libata: improve post-reset device ready test
Date: Sat, 10 May 2008 20:07:24 -0400	[thread overview]
Message-ID: <482638BC.8040001@garzik.org> (raw)
In-Reply-To: <20080510235149.GA4751@martell.zuzino.mipt.ru>

Alexey Dobriyan wrote:
> Gentlemen,
> 
> the following patch causes libata errors in dmesg (which I can ignore)
> and much longer bootup because of resets (which is irritating).

> 78ab88f04f44bed566d51dce0c7cbfeff6449a06 is first bad commit
> commit 78ab88f04f44bed566d51dce0c7cbfeff6449a06
> Author: Tejun Heo <htejun@gmail.com>
> Date:   Thu May 1 23:41:41 2008 +0900
> 
>     libata: improve post-reset device ready test


The fix was sent to Linus yesterday.

	Jeff



      reply	other threads:[~2008-05-11  0:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-10 23:51 libata: improve post-reset device ready test Alexey Dobriyan
2008-05-11  0:07 ` 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=482638BC.8040001@garzik.org \
    --to=jeff@garzik.org \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=htejun@gmail.com \
    --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).