From: "J.A. Magallon" <jamagallon@able.es>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: Alan Cox <alan@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19pre8-ac3 -- thread_info?
Date: Wed, 15 May 2002 16:04:55 +0200 [thread overview]
Message-ID: <20020515140455.GA2186@werewolf.able.es> (raw)
In-Reply-To: <200205141244.g4ECi6P29886@devserv.devel.redhat.com> <87ptzxlnzn.fsf@peder.flower>
On 2002.05.15 Jan Nieuwenhuizen wrote:
>
>It seems that 2.4.19pre8-ac3 introduced the use of thread_info, but
>it's not defined in sched.h?
>
>Greetings,
>Jan.
>
>gcc -D__KERNEL__ -I/var/src/linux-2.4/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4 -nostdinc -I /usr/lib/gcc-lib/i386-linux/2.95.4/include -DKBUILD_BASENAME=sched -fno-omit-frame-pointer -O2 -c -o sched.o sched.c
>sched.c: In function `migration_thread':
>sched.c:1595: structure has no member named `thread_info'
>sched.c:1600: structure has no member named `thread_info'
>sched.c:1606: structure has no member named `thread_info'
>sched.c:1574: warning: `cpu_src' might be used uninitialized in this function
>make[2]: *** [sched.o] Error 1
>
Sure it has been added ?
It can be the O1-sched patch or the O1-updates from rml, when extracted from
2.5 still use that.
Just change every occurence of:
p->thread_info->cpu
to
p->cpu.
Hope this helps.
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.3 (Cooker) for i586
Linux werewolf 2.4.19-pre8-jam2 #3 SMP lun may 13 00:49:15 CEST 2002 i686
next prev parent reply other threads:[~2002-05-15 14:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 12:44 Linux 2.4.19pre8-ac3 Alan Cox
2002-05-14 13:11 ` Tomas Szepe
2002-05-14 21:27 ` skidley
2002-05-14 22:50 ` Tomas Szepe
2002-05-15 1:19 ` Alan Cox
2002-05-14 13:16 ` Christoph Hellwig
2002-05-14 16:00 ` Kasper Dupont
2002-05-14 21:28 ` Diego Calleja
2002-05-15 10:11 ` Linux 2.4.19pre8-ac3 -- thread_info? Jan Nieuwenhuizen
2002-05-15 14:04 ` J.A. Magallon [this message]
2002-05-15 16:34 ` Robert Love
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=20020515140455.GA2186@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@redhat.com \
--cc=janneke@gnu.org \
--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.