From: "Tarkan Erimer" <tarkane@solmaz.com.tr>
To: "Linux" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.18-pre9-xfs-shawn4 - kmem_cache_alloc oops
Date: Tue, 12 Feb 2002 17:26:57 +0200 [thread overview]
Message-ID: <023301c1b3d9$b57e1a20$040010ac@LocalHost> (raw)
In-Reply-To: <20020212141007.B223@dagb> <1013523257.262.3.camel@unaropia> <01f601c1b3d6$c94ca060$040010ac@LocalHost> <1013527094.263.17.camel@unaropia>
> It is in the works. I'm trying to iron out any buglets that remain and
> make sure that I don't break anything in the process ;-)
thanks.. Be sure, when it is out; i will be the first guy, who tries it 8-)
Tarkan
next prev parent reply other threads:[~2002-02-12 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020212141007.B223@dagb>
2002-02-12 14:13 ` 2.4.18-pre9-xfs-shawn4 - kmem_cache_alloc oops Shawn Starr
2002-02-12 15:06 ` Tarkan Erimer
2002-02-12 15:18 ` Shawn Starr
2002-02-12 15:26 ` Tarkan Erimer [this message]
2002-02-12 20:14 ` Andrew Morton
2002-02-12 20:23 ` Shawn Starr
2002-02-12 14:28 ` Shawn Starr
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='023301c1b3d9$b57e1a20$040010ac@LocalHost' \
--to=tarkane@solmaz.com.tr \
--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