public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Cliff Albert <cliff@oisec.net>
Cc: Linux kernel <linux-kernel@vger.kernel.org>, J Sloan <jjs@toyota.com>
Subject: Re: Updated Linux kernel preemption patches
Date: 27 Aug 2001 17:40:40 -0400	[thread overview]
Message-ID: <998948441.12267.9.camel@phantasy> (raw)
In-Reply-To: <20010827232415.A670@oisec.net>
In-Reply-To: <998877465.801.19.camel@phantasy> <20010827093835.A15153@oisec.net> <3B8AA02D.6F7561AB@lexus.com> <998941465.1993.9.camel@phantasy> <998947154.11860.30.camel@phantasy>  <20010827232415.A670@oisec.net>

On Mon, 2001-08-27 at 17:24, Cliff Albert wrote:
> I ALWAYS run make dep && make clean && make bzImage when building a new 
> kernel 

OK, so that is not the problem...

> It still borks, probably you are having other options in your kernel config
> and sections you don't use may depend on dec_and_lock

No, I have places in my kernel where atomic_dec_and_lock is used.  In
fact, one of the functions I was pasted where it broke was mmput() in
kernel.S (i think from fork.c).  I have that function, and it uses
atomic_dec_and_lock...

So the problem is most certainly something to do with your configuration
not getting the dependency right to use atomic_dec_and_lock

Out of curiosity, what CONFIG CPU are you defined to use? 
 
> First get it to work, and then spend time on keeping it current with alan's
> and linus' tree.

I am working, but it is not my code.  I am merely trying to keep it in
sync with the trees.  I am trying to get it working for those who it
does not compile for, but it works for me and others, so it is hard.

-- 
Robert M. Love
rml at ufl.edu
rml at tech9.net


  reply	other threads:[~2001-08-27 21:40 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
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 [this message]
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=998948441.12267.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox