From: Michael Dunsky <michael.dunsky@p4all.de>
To: "Elgar, Jeremy" <JElgar@ndsuk.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Mixing Patches: pre-emptive + xfs
Date: Mon, 26 Nov 2001 21:23:52 +0100 [thread overview]
Message-ID: <3C02A4D8.5010405@p4all.de> (raw)
In-Reply-To: <F128989C2E99D4119C110002A507409801C53035@topper.hrow.ndsuk.com>
Elgar, Jeremy wrote:
> Hello
> 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.
>
> Cheers
>
> Jeremy
>
> (BTW both are 2.4.14)
Well - it works.
I have both patches runnig here (installed the xfs-patches and after
that the preempt-2.4.14-2 - only 2 or 3 minor offsets while patching).
System "feels" fluid now - but my UT crashes hard while using that
kernel :( Seems it doesn't like it. But while normal work no problems
detected until now...
ciao
Michael
next prev parent reply other threads:[~2001-11-26 20:22 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 [this message]
2001-11-26 20:26 ` Robert Love
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=3C02A4D8.5010405@p4all.de \
--to=michael.dunsky@p4all.de \
--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