From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IDE problems with rmmod ide-cd
Date: Thu, 28 Apr 2005 19:25:42 +0200 [thread overview]
Message-ID: <20050428172541.GN1876@suse.de> (raw)
In-Reply-To: <1114706653.18330.212.camel@localhost.localdomain>
On Thu, Apr 28 2005, Alan Cox wrote:
> If you rmmod ide-cd in 2.6.12rc3 it issues a cache flush command to the
> drive. Thankfully the bogus command this time is an ATAPI cache flush
> not an ATA one so won't do any major harm but its still wrong as the
> device is not a writer or packet mode capable (its a random DVD reader
> holding a music CD)
The problem you are thinking of was also an ATAPI cache flush command,
so I'm not so sure I would call it harmless... I haven't changed
anything in there recently, Bart?
--
Jens Axboe
next prev parent reply other threads:[~2005-04-28 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 16:44 IDE problems with rmmod ide-cd Alan Cox
2005-04-28 17:25 ` Jens Axboe [this message]
2005-04-28 20:46 ` Bartlomiej Zolnierkiewicz
2005-04-28 21:51 ` Alan Cox
2005-04-28 22:20 ` Bartlomiej Zolnierkiewicz
2005-04-28 22:24 ` Alan Cox
2005-04-29 14:03 ` Alan Cox
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=20050428172541.GN1876@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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