All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@linux.org.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, debian-powerpc@lists.debian.org
Subject: Re: OOPS: cdrecord -scanbus on benh 2.5 tree causes oops
Date: Wed, 21 Jan 2004 22:18:06 +1100	[thread overview]
Message-ID: <1074683884.2623.4.camel@willster> (raw)
In-Reply-To: <1074634670.739.24.camel@gaston>

On Wed, 2004-01-21 at 08:37, Benjamin Herrenschmidt wrote:
> As Colin says, ide-scsi is deprecated :) Anyway, it shouldn't oops.

known and noted - but the point was yeah, shouldn't oops.

> and let me know if the problem is still there in my current 2.6.1-ben1 ?

Seems to be okay in your current tree (rsyned today). Although I just
found a HFS related oops....

-- 
Stewart Smith (stewart@linux.org.au)
Vice President, Linux Australia



       reply	other threads:[~2004-01-21 11:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1074607152.21539.15.camel@willster>
     [not found] ` <1074634670.739.24.camel@gaston>
2004-01-21 11:18   ` Stewart Smith [this message]
2004-01-21 13:25     ` OOPS: cdrecord -scanbus on benh 2.5 tree causes oops 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=1074683884.2623.4.camel@willster \
    --to=stewart@linux.org.au \
    --cc=benh@kernel.crashing.org \
    --cc=debian-powerpc@lists.debian.org \
    --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.