public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: John Levon <movement@marcelothewonderpenguin.com>,
	Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org, davej@suse.de
Subject: Re: [PATCH] Fix 2.5.3pre reiserfs BUG() at boot time
Date: Fri, 25 Jan 2002 21:46:06 +0300	[thread overview]
Message-ID: <3C51A7EE.1010108@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0201251006220.1632-100000@penguin.transmeta.com>

We are preparing a large set of patches (each to be sent as a separate 
email per your SOP, but all tested together in a thorough testing 
procedure), which includes this patch, plus the kdev fix, plus all 2.4 
fixes.  We expect to send it out on monday, we just found a bug in the 
patches as a set that was not present in them individually.

Hans



  parent reply	other threads:[~2002-01-25 18:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25 17:28 [PATCH] Fix 2.5.3pre reiserfs BUG() at boot time Andi Kleen
2002-01-25 18:01 ` John Levon
2002-01-25 18:08   ` Linus Torvalds
2002-01-25 18:31     ` Andreas Dilger
2002-01-25 18:46     ` Hans Reiser [this message]
2002-01-25 19:49     ` Andi Kleen
2002-01-25 20:38       ` Andreas Dilger
2002-01-25 22:15         ` Andi Kleen
2002-01-25 22:32           ` eth0: NULL pointer encountered in RX ring, skipping Andrea Ferraris
2002-01-25 22:59             ` Jeff Garzik
2002-01-26 10:11               ` Andrea Ferraris
2002-01-26 15:24                 ` OPS: " Andrea Ferraris
2002-01-25 22:41           ` [PATCH] Fix 2.5.3pre reiserfs BUG() at boot time Andreas Dilger
2002-01-26  7:24           ` Kai Henningsen
2002-01-27 23:02           ` Alessandro Suardi
2002-01-28  0:01             ` Andi Kleen
2002-01-28 11:07               ` Jens Axboe
2002-01-28 14:53                 ` Andi Kleen
2002-01-28 14:54                   ` Jens Axboe
2002-01-29 13:14               ` Alessandro Suardi

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=3C51A7EE.1010108@namesys.com \
    --to=reiser@namesys.com \
    --cc=ak@suse.de \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=movement@marcelothewonderpenguin.com \
    --cc=torvalds@transmeta.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