From: Jeff Mahoney <jeffm@suse.com>
To: Sergei Shtylyov <sshtylyov@mvista.com>
Cc: Jeff Garzik <jgarzik@redhat.com>, Tejun Heo <tj@kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: Pioneer DVR-216D can't do SETXFER
Date: Tue, 19 Apr 2011 18:06:20 -0400 [thread overview]
Message-ID: <4DAE075C.5050707@suse.com> (raw)
In-Reply-To: <4DADF903.5000503@ru.mvista.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/19/2011 05:05 PM, Sergei Shtylyov wrote:
> Hello.
>
> On 19-04-2011 19:13, Jeff Mahoney wrote:
>
>> Commit 4a5610a04d415ed94af75bb1159d2621d62c8328 fixed an issue with
>
> Please also specify that commit's summary in parens -- for the human
> readers.
>
>> the Pioneer DVR-212D not handling SETXFER correctly. An openSUSE user
>> reported a similar issue with his DVR-216D that the NOSETXFER horkage
>> worked around for him as well.
>
>> This patch adds the DVR-216D (1.08) to the horkage list for NOSETXFER.
>
>> The issue was reported at:
>> https://bugzilla.novell.com/show_bug.cgi?id=679143
>
>> Reported-by: Volodymyr Kyrychenko <vladimir.kirichenko@gmail.com>
>> Signed-off-by: Jeff Mahoney <jeffm@suse.com>
The issue and summary are identical except for the model number.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAk2uB1wACgkQLPWxlyuTD7Lk+ACfRWh9cqciafuYSCrTsA4/Ccci
aWcAniDuTUmJbbPGAYt6TKnQLzYiNQR5
=xpeL
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-04-19 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 15:13 [PATCH] libata: Pioneer DVR-216D can't do SETXFER Jeff Mahoney
2011-04-19 21:05 ` Sergei Shtylyov
2011-04-19 22:06 ` Jeff Mahoney [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-20 12:44 fl-00
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=4DAE075C.5050707@suse.com \
--to=jeffm@suse.com \
--cc=jgarzik@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@mvista.com \
--cc=tj@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).