From: Andi Kleen <ak@muc.de>
To: Oleg Drokin <green@namesys.com>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Slab cache name fixes / reiserfs boot bug fix.
Date: Thu, 31 Jan 2002 17:08:12 +0100 [thread overview]
Message-ID: <20020131170811.A1367@averell> (raw)
In-Reply-To: <20020131002937.A1372@averell> <20020131100219.A11046@namesys.com>
In-Reply-To: <20020131100219.A11046@namesys.com>
On Thu, Jan 31, 2002 at 08:02:19AM +0100, Oleg Drokin wrote:
> Hello!
>
> On Thu, Jan 31, 2002 at 12:29:37AM +0100, Andi Kleen wrote:
> > slab names. This fixes the reiserfs boot time BUG() that is still in 2.5.3.
> Sorry, What BUG()? The one I know that was related to "reiserfs_inode_cache"
It seems to be gone already, yes. Sorry for the confusion.
Anyways, the slab name patch should be the right thing to fix the interface.
-Andi
prev parent reply other threads:[~2002-01-31 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 23:29 [PATCH] Slab cache name fixes / reiserfs boot bug fix Andi Kleen
[not found] ` <Pine.LNX.4.33.0201301548100.14950-100000@penguin.transmeta.com>
2002-01-30 23:59 ` Andi Kleen
2002-01-31 0:48 ` Andi Kleen
[not found] ` <20020131100219.A11046@namesys.com>
2002-01-31 16:08 ` Andi Kleen [this message]
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=20020131170811.A1367@averell \
--to=ak@muc.de \
--cc=green@namesys.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox