From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
alan@lxorguk.ukuu.org.uk, rjw@sisk.pl, akpm@linux-foundation.org
Subject: Re: [PATCH 1/2] libata-sff: fix 32-bit PIO ATAPI regression
Date: Tue, 17 Feb 2009 03:20:26 +0300 [thread overview]
Message-ID: <499A02CA.7050509@ru.mvista.com> (raw)
In-Reply-To: <4999FD1A.3080407@pobox.com>
Hello.
Jeff Garzik wrote:
>> Commit 871af1210f13966ab911ed2166e4ab2ce775b99d (libata: Add 32bit
>> PIO support)
>> has caused all kinds of errors on the ATAPI devices, so it has been
>> empirically
It started to look as we still don't really know what caused all these
errors... :-/
MBR, Sergei
prev parent reply other threads:[~2009-02-17 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 19:24 [PATCH 1/2] libata-sff: fix 32-bit PIO ATAPI regression Sergei Shtylyov
2009-02-16 23:56 ` Jeff Garzik
2009-02-17 0:20 ` Sergei Shtylyov [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=499A02CA.7050509@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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).