From: Robert Love <rml@tech9.net>
To: "Elgar, Jeremy" <JElgar@ndsuk.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Mixing Patches: pre-emptive + xfs
Date: 26 Nov 2001 15:26:48 -0500 [thread overview]
Message-ID: <1006806412.992.8.camel@phantasy> (raw)
In-Reply-To: <F128989C2E99D4119C110002A507409801C53035@topper.hrow.ndsuk.com>
In-Reply-To: <F128989C2E99D4119C110002A507409801C53035@topper.hrow.ndsuk.com>
On Mon, 2001-11-26 at 06:13, Elgar, Jeremy wrote:
> Just wondering if anyone has try using these two patches together (or is
> this a really bad idea)
>
> I'm thinking of adding the pre-emptive patch to my laptop and desk top.
Although I haven't done any formal testing on XFS, I have heard XFS and
preempt-kernel work fine together from a couple of users.
The only problem reported was a compile error, which Keith Owens merged
a fix for. If you do have problems, report them and perhaps we can
help.
Robert Love
next prev parent reply other threads:[~2001-11-26 20:27 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 [this message]
2001-12-02 7:23 ` Anuradha Ratnaweera
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=1006806412.992.8.camel@phantasy \
--to=rml@tech9.net \
--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