From: Anuradha Ratnaweera <anuradha@gnu.org>
To: "Elgar, Jeremy" <JElgar@ndsuk.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Mixing Patches: pre-emptive + xfs
Date: Sun, 2 Dec 2001 13:23:13 +0600 [thread overview]
Message-ID: <20011202132313.A5555@bee.lk> (raw)
In-Reply-To: <F128989C2E99D4119C110002A507409801C53035@topper.hrow.ndsuk.com>
In-Reply-To: <F128989C2E99D4119C110002A507409801C53035@topper.hrow.ndsuk.com>; from JElgar@ndsuk.com on Mon, Nov 26, 2001 at 11:13:33AM -0000
On Mon, Nov 26, 2001 at 11:13:33AM -0000, Elgar, Jeremy wrote:
>
> Just wondering if anyone has try using these two patches together (or is this
> a really bad idea)
I run xfs+preempt on a headless firewall machine for quite some time without
any appearent problem.
Cheers,
Anuradha
--
Debian GNU/Linux (kernel 2.4.16)
Your true value depends entirely on what you are compared with.
prev parent reply other threads:[~2001-12-02 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 11:13 Mixing Patches: pre-emptive + xfs Elgar, Jeremy
2001-11-26 15:53 ` listmail
2001-11-26 20:23 ` Michael Dunsky
2001-11-26 20:26 ` Robert Love
2001-12-02 7:23 ` Anuradha Ratnaweera [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=20011202132313.A5555@bee.lk \
--to=anuradha@gnu.org \
--cc=JElgar@ndsuk.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