From: Nigel Rantor <wiggly@wiggly.org>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cdrom ripping / dropping to dingle frame dma
Date: Tue, 15 Jun 2004 21:47:15 +0100 [thread overview]
Message-ID: <40CF6053.3020105@wiggly.org> (raw)
In-Reply-To: <20040615203828.GA12504@suse.de>
Jens Axboe wrote:
> It did not, and it didn't fix the issue completely. My plan is to add a
> counter just checking if we succeeded doing some dma ripping already,
> in which case there's no point to falling back to lesser methods. That
> should be way more reliable than checking sense and making up our on
> rules based on that.
>
> I'll get a patch out tomorrow.
Cool, thanks for the reply. I'm quite happy to go to 2.6.7 if that's
what you'll be patching against.
Are you still looking for people who can reproduce this problem? If so
I'll try and find a couple of the CDs that I have that kill ripping now
on this kernel before applying any patches you come up with.
Regards,
N
next prev parent reply other threads:[~2004-06-15 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 20:17 cdrom ripping / dropping to dingle frame dma Nigel Rantor
2004-06-15 20:38 ` Jens Axboe
2004-06-15 20:47 ` Nigel Rantor [this message]
2004-06-15 20:49 ` Jens Axboe
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=40CF6053.3020105@wiggly.org \
--to=wiggly@wiggly.org \
--cc=axboe@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.