From: Robert Love <rml@tech9.net>
To: J Sloan <jjs@toyota.com>
Cc: Cliff Albert <cliff@oisec.net>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Updated Linux kernel preemption patches
Date: 27 Aug 2001 15:44:21 -0400 [thread overview]
Message-ID: <998941465.1993.9.camel@phantasy> (raw)
In-Reply-To: <3B8AA02D.6F7561AB@lexus.com>
In-Reply-To: <998877465.801.19.camel@phantasy> <20010827093835.A15153@oisec.net> <3B8AA02D.6F7561AB@lexus.com>
On Mon, 2001-08-27 at 15:31, J Sloan wrote:
> I get the same error -
>
> RH 7.1 + updates and bits of rawhide -
I am looking into this, but I do not have this problem (which is odd).
The patch wraps one define of atomic_dec_and_lock in an #ifndef
CONFIG_PREEMPT, but I assume there is another defination elsewhere. For
whatever reason, my kernel compiles fine.
I am going to update the patch to 2.4.9-ac2, give that a try.
Wait a second...you are _ENABLING_ the configure option, right? Always
run `make oldconfig' !!! If you are not, in this case, the patch is
breaking compiles where CONFIG_PREEMPT is not set...now I can fix that.
Please let me know.
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next prev parent reply other threads:[~2001-08-27 19:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 1:57 Updated Linux kernel preemption patches Robert Love
2001-08-27 3:06 ` Daniel Phillips
2001-08-27 3:09 ` Robert Love
2001-08-27 7:38 ` Cliff Albert
2001-08-27 13:46 ` Robert Love
2001-08-27 15:20 ` Cliff Albert
2001-08-27 19:31 ` J Sloan
2001-08-27 19:44 ` Robert Love [this message]
2001-08-27 21:12 ` Andrey Nekrasov
2001-08-27 21:35 ` Robert Love
2001-08-27 21:18 ` Robert Love
2001-08-27 21:24 ` Cliff Albert
2001-08-27 21:40 ` Robert Love
2001-08-27 23:06 ` Andrey Nekrasov
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=998941465.1993.9.camel@phantasy \
--to=rml@tech9.net \
--cc=cliff@oisec.net \
--cc=jjs@toyota.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.