public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Shane Shrybman <shrybman@sympatico.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@digeo.com>
Subject: Re: Can't find CDR device in -mm only
Date: Sat, 10 May 2003 18:41:02 +0200	[thread overview]
Message-ID: <20030510164102.GD837@suse.de> (raw)
In-Reply-To: <1052578016.2369.7.camel@mars.goatskin.org>

On Sat, May 10 2003, Shane Shrybman wrote:
> Hi Jens,
> 
> On Sat, 2003-05-10 at 05:20, Jens Axboe wrote:
> > On Fri, May 09 2003, Shane Shrybman wrote:
> > > Hi,
> > > 
> > > The problem first appeared in 2.5.68-mm3 and is not in mainline 2.5.69.
> > > It is present in all -mm releases since.
> > 
> > Curious. Looking at patches between .68-mm2 and -mm3 reveals nothing
> > major, in fact the only thing touching anything in that area seems to be
> > the dynamic request allocation patch. Could you try 2.5.69 with the
> > attached patch to verify that it still works (or doesn't)? There might
> > be a small offset in deadline-iosched.c, should be nothing to worry
> > about.
> 
> Still doesn't work with 2.5.69 + rq_dyn. The output from cdrecord is
> below.

Ah thanks, that kind of narrows it down then. I'll take a look at the
problem tomorrow, should be easy to reproduce. Thanks for reporting!

-- 
Jens Axboe


  reply	other threads:[~2003-05-10 16:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-10  3:37 Can't find CDR device in -mm only Shane Shrybman
2003-05-10  3:41 ` Andrew Morton
2003-05-10  3:50   ` Shane Shrybman
2003-05-10  9:20 ` Jens Axboe
2003-05-10 14:46   ` Shane Shrybman
2003-05-10 16:41     ` Jens Axboe [this message]
2003-05-14  7:43       ` Jens Axboe
2003-05-14 22:46         ` Shane Shrybman

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=20030510164102.GD837@suse.de \
    --to=axboe@suse.de \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shrybman@sympatico.ca \
    /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