mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: jijo@i-manila.com.ph (Federico Sevilla III)
Cc: reiserfs@devlinux.com (ReiserFS Mailing List),
	linux-kernel@vger.kernel.org (Linux Kernel Mailing List),
	alan@lxorguk.ukuu.org.uk (Alan Cox)
Subject: Re: unmount issues with 2.4.5-ac5, 3ware, and ReiserFS (was: kernel-2.4.5
Date: Thu, 31 May 2001 22:32:34 +0100 (BST)	[thread overview]
Message-ID: <E155a3W-00084H-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.21.0106010147060.1228-100000@kalapati.jijo.local> from "Federico Sevilla III" at Jun 01, 2001 02:23:15 AM

> I'm staying on 2.4.5-ac5 for whatever it's worth (putting my life on the
> line for the community? kidding...) and will report anything new. I will
> be on the lookout for later ac patches, 2.4.6 ... and hopefully anything
> anybody can share with me about this. I hope we'll see an end to these

Can you tell me if 2.4.5-ac4 is ok. ac5 has a small 'obviously correct'
reiserfs module unload change that seems the first suspect


  reply	other threads:[~2001-05-31 21:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B167AFD.EC1897E1@namesys.com>
2001-05-31 18:23 ` unmount issues with 2.4.5-ac5, 3ware, and ReiserFS (was: kernel-2.4.5 bug) Federico Sevilla III
2001-05-31 21:32   ` Alan Cox [this message]
2001-05-31 22:04     ` unmount issues with 2.4.5-ac5, 3ware, and ReiserFS (was: kernel-2.4.5 Jordan
2001-06-01  8:56       ` thunder7
2001-06-01  9:37         ` Lech Szychowski
2001-06-01 13:48           ` Lech Szychowski
2001-06-01 17:10         ` Hans Reiser
2001-06-01 17:47           ` unmount issues with 2.4.5-ac5, 3ware, and ReiserFS (was: Alan Cox
2001-06-01 18:05           ` unmount issues with 2.4.5-ac5, 3ware, and ReiserFS (was: kernel-2.4.5 Alexander Viro
2001-06-02  6:13             ` Hans Reiser

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=E155a3W-00084H-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jijo@i-manila.com.ph \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs@devlinux.com \
    /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

all inboxes | Powered by JetHome®