The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Nigel Rantor <wiggly@wiggly.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cdrom ripping / dropping to dingle frame dma
Date: Tue, 15 Jun 2004 22:49:09 +0200	[thread overview]
Message-ID: <20040615204908.GA12603@suse.de> (raw)
In-Reply-To: <40CF6053.3020105@wiggly.org>

On Tue, Jun 15 2004, Nigel Rantor wrote:
> 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.

I usually patch against current -BK, so if you run latest -bkX snapshot
you should be fine. The risk of rejects isn't too big in this area, so
2.6.7-rc3 should be adequate.

> 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.

If you can find an easily reproducable test case to run on a patch,
that's certainly very helpful.

-- 
Jens Axboe


      reply	other threads:[~2004-06-15 20:50 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
2004-06-15 20:49     ` Jens Axboe [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=20040615204908.GA12603@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wiggly@wiggly.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