linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bill Davidsen <davidsen@tmr.com>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-ide@vger.kernel.org
Subject: Re: IDE CDROM tail read errors
Date: Wed, 12 Apr 2006 09:57:39 +0100	[thread overview]
Message-ID: <1144832260.1952.13.camel@localhost.localdomain> (raw)
In-Reply-To: <4432C460.3080606@tmr.com>

On Maw, 2006-04-04 at 15:09 -0400, Bill Davidsen wrote:
> Any hope in hell of getting this fixed? It's been broken for too long to 
> remember. IIRC the problem is that on a read which hits EOF, instead of 

The libata layer doesn't have the problem. So it will get fixed as the
libata PATA stuff gets upstream and merged


      reply	other threads:[~2006-04-12  8:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29 19:11 IDE CDROM tail read errors Krzysztof Halasa
2006-03-30  8:19 ` Jan Engelhardt
2006-04-02 10:55   ` Krzysztof Halasa
2006-04-02 18:13     ` Jan Engelhardt
2006-03-30 11:18 ` Alan Cox
2006-04-02 10:50   ` Krzysztof Halasa
2006-04-04 19:09   ` Bill Davidsen
2006-04-12  8:57     ` Alan Cox [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=1144832260.1952.13.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=davidsen@tmr.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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).