From: David Miller <davem@davemloft.net>
To: sshtylyov@ru.mvista.com
Cc: linux-ide@vger.kernel.org, stable@kernel.org, bzolnier@gmail.com,
alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH 1/2] hpt366: add debounce delay to cable_detect() method
Date: Mon, 27 Sep 2010 11:00:50 -0700 (PDT) [thread overview]
Message-ID: <20100927.110050.232902423.davem@davemloft.net> (raw)
In-Reply-To: <201009271808.15710.sshtylyov@ru.mvista.com>
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Date: Mon, 27 Sep 2010 18:08:15 +0400
> Alan Cox reported that cable detection sometimes works unreliably
> for HPT3xxN and that the issue is fixed by adding debounce delay
> as used by the vendor drivers.
>
> While at it, get rid of unneeded parens/space in the vicinity...
>
> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Applied.
prev parent reply other threads:[~2010-09-27 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 14:08 [PATCH 1/2] hpt366: add debounce delay to cable_detect() method Sergei Shtylyov
2010-09-27 18:00 ` David Miller [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=20100927.110050.232902423.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
--cc=stable@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).