From: Martin Costabel <costabel@wanadoo.fr>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Tom Rini <trini@kernel.crashing.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Hollis Blanchard <hollis-lists@austin.rr.com>,
Giuliano Pochini <pochini@denise.shiny.it>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: hfs cdrom broken in 2.4.13pre
Date: Tue, 23 Oct 2001 13:04:13 +0200 [thread overview]
Message-ID: <3BD54EAD.9F292DAE@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.4.33.0110231203080.29506-100000@opal.biophys.uni-duesseldorf.de
Michael Schmitz wrote:
> Besides - hasn't HFS CDROM support been broken since a long time? Or was
> that HFS? :-)
There was a slightly more informed discussion about this in August 2000
on the linux-kernel list. The bug was found in the scsi code and fixed
shortly afterwards by Jens Axboe, IIRC. This was in the good old days
when people thought the upcoming 2.4 kernel series would be stable and
bleeding-edge development would happen in a 2.5 series.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-23 11:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011022155617.B6673@cpe-24-221-152-185.az.sprintbbd.net>
2001-10-23 10:08 ` hfs cdrom broken in 2.4.13pre Michael Schmitz
2001-10-23 11:04 ` Martin Costabel [this message]
2001-10-23 11:26 ` Michael Schmitz
2001-10-23 13:16 ` Giuliano Pochini
2001-10-23 13:26 ` Alan Cox
2001-10-23 15:24 ` Michael Schmitz
2001-10-23 15:52 ` Alan Cox
2001-10-23 16:31 ` Michael Schmitz
2001-10-23 16:51 ` Alan Cox
2001-10-23 20:08 ` Michael Schmitz
2001-10-23 20:49 ` Alan Cox
2001-10-24 7:21 ` Michael Schmitz
2001-10-23 19:59 ` Benjamin Herrenschmidt
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=3BD54EAD.9F292DAE@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hollis-lists@austin.rr.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=pochini@denise.shiny.it \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
--cc=trini@kernel.crashing.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).