From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] ide-iops: fix odd-length ATAPI PIO transfers
Date: Thu, 5 Mar 2009 16:03:36 +0100 [thread overview]
Message-ID: <200903051603.37438.bzolnier@gmail.com> (raw)
In-Reply-To: <200903051736.34002.sshtylyov@ru.mvista.com>
On Thursday 05 March 2009, Sergei Shtylyov wrote:
> Commit 9567b349f7e7dd7e2483db99ee8e4a6fe0caca38 (ide: merge ->atapi_*put_bytes
> and ->ata_*put_data methods) introduced a regression WRT the odd-length ATAPI
> PIO transfers -- the final word didn't get written (causing command timeouts).
>
> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
applied, thanks!
prev parent reply other threads:[~2009-03-05 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 14:36 [PATCH] ide-iops: fix odd-length ATAPI PIO transfers Sergei Shtylyov
2009-03-05 15:03 ` Bartlomiej Zolnierkiewicz [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=200903051603.37438.bzolnier@gmail.com \
--to=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).