public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Olaf Hering <olh@suse.de>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: 2.6.22: oops in sbp2_remove_device
Date: Thu, 02 Aug 2007 05:38:54 +0200	[thread overview]
Message-ID: <46B151CE.4000204@s5r6.in-berlin.de> (raw)
In-Reply-To: <20070801231703.GA25672@suse.de>

Olaf Hering wrote:
> On Wed, Aug 01, Stefan Richter wrote:
>> Revert commit 0555659d63c285ceb7ead3115532e1b71b0f27a7 from 2.6.22-rc1.

> This change fixes the oops, and I can access the drive again.

Did it oops always or only sometimes?
-- 
Stefan Richter
-=====-=-=== =--- ---=-
http://arcgraph.de/sr/

  reply	other threads:[~2007-08-02  3:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01 17:57 2.6.22: oops in sbp2_remove_device Olaf Hering
2007-08-01 18:30 ` Stefan Richter
2007-08-01 23:17   ` Olaf Hering
2007-08-02  3:38     ` Stefan Richter [this message]
2007-08-02  8:26       ` Olaf Hering

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=46B151CE.4000204@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=olh@suse.de \
    /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