From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH #upstream-fixes] libata: ignore deverr on SETXFER if mode is configured
Date: Thu, 7 Feb 2008 01:45:39 +0000 [thread overview]
Message-ID: <20080207014539.58f7581e@core> (raw)
In-Reply-To: <47AA6010.30003@gmail.com>
On Thu, 07 Feb 2008 10:34:08 +0900
Tejun Heo <htejun@gmail.com> wrote:
> Some controllers (VIA CX700) raise device error on SETXFER even after
> mode configuration succeeded. Update ata_dev_set_mode() such that
> device error is ignored if transfer mode is configured correctly. To
> implement this, device is revalidated even after device error on
> SETXFER.
>
> This fixes kernel bugzilla bug 8563.
Tidy
Acked-by: Alan Cox <alan@redhat.com>
next prev parent reply other threads:[~2008-02-07 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 1:34 [PATCH #upstream-fixes] libata: ignore deverr on SETXFER if mode is configured Tejun Heo
2008-02-07 1:45 ` Alan Cox [this message]
2008-02-11 19:30 ` 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=20080207014539.58f7581e@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--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).