From: Shawn Starr <shawn.starr@datawire.net>
To: Tarkan Erimer <tarkane@solmaz.com.tr>
Cc: Linux <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.18-pre9-xfs-shawn4 - kmem_cache_alloc oops
Date: 12 Feb 2002 10:18:14 -0500 [thread overview]
Message-ID: <1013527094.263.17.camel@unaropia> (raw)
In-Reply-To: <01f601c1b3d6$c94ca060$040010ac@LocalHost>
In-Reply-To: <20020212141007.B223@dagb> <1013523257.262.3.camel@unaropia> <01f601c1b3d6$c94ca060$040010ac@LocalHost>
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 ;-)
Shawn.
On Tue, 2002-02-12 at 10:06, Tarkan Erimer wrote:
> Hi Shawn,
>
> Do you plan to add XFS support to .mjc patches ?
> If so, I would be soo grateful.
>
> Tarkan
>
> ----- Original Message -----
> From: Shawn Starr <spstarr@sh0n.net>
> To: Dag Bakke <dag@bakke.com>
> Cc: Linux <linux-kernel@vger.kernel.org>; xfs <linux-xfs@oss.sgi.com>
> Sent: Tuesday, February 12, 2002 4:13 PM
> Subject: Re: 2.4.18-pre9-xfs-shawn4 - kmem_cache_alloc oops
>
>
> > Interesting, I have CONFIG_PNPBIOS on.
> > What other filesystems do you have or is it just XFS only?
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Shawn Starr
Developer Support Engineer
Datawire Communication Networks Inc.
10 Carlson Court, Suite 300
Toronto, ON, M9W 6L2
T: 416-213-2001 ext 179 F: 416-213-2008
next prev parent reply other threads:[~2002-02-12 15:15 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 [this message]
2002-02-12 15:26 ` Tarkan Erimer
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=1013527094.263.17.camel@unaropia \
--to=shawn.starr@datawire.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tarkane@solmaz.com.tr \
/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