From: Robert Love <rml@tech9.net>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Norbert Kiesel <nkiesel@tbdnetworks.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCHSET] Linux 2.4.19-pre7-jam4
Date: 22 Apr 2002 08:44:01 -0400 [thread overview]
Message-ID: <1019479445.940.4.camel@phantasy> (raw)
In-Reply-To: <20020422074013.GA7294@werewolf.able.es>
On Mon, 2002-04-22 at 03:40, J.A. Magallon wrote:
> >1) sched.c complains about missing local_bh_count, TQUEUE_BH, ...
you need to #include linux/interrupts.h in sched.c
> Yup, there are files not covered by 20-sched-O1-rml-1.
> Fast search:
>
> werewolf:/usr/src/linux# grep -r SCHED_YIELD *
> arch/alpha/mm/fault.c: current->policy |= SCHED_YIELD;
> arch/mips/mm/fault.c: tsk->policy |= SCHED_YIELD;
> arch/ppc/mm/fault.c: current->policy |= SCHED_YIELD;
> arch/m68k/mm/fault.c: current->policy |= SCHED_YIELD;
> arch/arm/mm/fault-common.c: tsk->policy |= SCHED_YIELD;
> arch/sh/mm/fault.c: current->policy |= SCHED_YIELD;
> arch/ia64/mm/fault.c: current->policy |= SCHED_YIELD;
> arch/mips64/mm/fault.c: tsk->policy |= SCHED_YIELD;
> arch/s390/mm/fault.c: tsk->policy |= SCHED_YIELD;
> arch/s390x/mm/fault.c: tsk->policy |= SCHED_YIELD;
> init/do_mounts.c: current->policy |= SCHED_YIELD;
I did not touch the arch-dependent code because there are other changes
the arches require that need to be made ...
Robert Love
next prev parent reply other threads:[~2002-04-22 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 6:30 [PATCHSET] Linux 2.4.19-pre7-jam4 Norbert Kiesel
2002-04-22 7:40 ` J.A. Magallon
2002-04-22 12:44 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-22 1:11 J.A. Magallon
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=1019479445.940.4.camel@phantasy \
--to=rml@tech9.net \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nkiesel@tbdnetworks.com \
/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