From: Robert Love <rml@tech9.net>
To: Arkadiy Chapkis - Arc <achapkis@mail.dls.net>
Cc: LINUX-KERNEL@vger.kernel.org
Subject: Re: thread_info implementation
Date: 11 Feb 2002 15:19:27 -0500 [thread overview]
Message-ID: <1013458767.6785.459.camel@phantasy> (raw)
In-Reply-To: <00A09679.2A996F5D.164@mail.dls.net>
In-Reply-To: <00A09679.2A996F5D.164@mail.dls.net>
On Mon, 2002-02-11 at 12:39, Arkadiy Chapkis - Arc wrote:
> In file included from
> /usr/local/src/test/linux-2.5.4/include/linux/spinlock.h:7,
> from
> /usr/local/src/test/linux-2.5.4/include/linux/module.h:11,
> from loop.c:55:
> /usr/local/src/test/linux-2.5.4/include/linux/thread_info.h:10:29:
> asm/thread_info.h: No such file or directory
This is known. I don't believe any arches except i386 and SPARC64 are
using the new thread_info / task_struct implementation introduced during
2.5.4-pre.
I think I saw some changesets from Jeff Garzik wrt alpha thread_info
support, so perhaps in 2.5.5-pre1.
Robert Love
next prev parent reply other threads:[~2002-02-11 20:20 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 17:39 thread_info implementation Arkadiy Chapkis - Arc
2002-02-11 20:19 ` Robert Love [this message]
2002-02-11 20:42 ` Luigi Genoni
2002-02-11 20:48 ` Robert Love
2002-02-11 23:37 ` Jeff Garzik
2002-02-11 23:49 ` Richard Henderson
2002-02-12 0:09 ` Dave Jones
2002-02-12 0:20 ` Jeff Garzik
2002-02-12 0:24 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2002-02-11 21:08 Roman Zippel
2002-02-11 20:50 ` Anton Blanchard
2002-02-12 0:46 ` David S. Miller
2002-02-12 0:57 ` Roman Zippel
2002-02-12 0:57 ` David S. Miller
2002-02-12 1:10 ` Roman Zippel
2002-02-12 13:01 ` Bjorn Wesen
2002-02-12 13:49 ` David S. Miller
2002-02-12 1:01 ` David Mosberger
2002-02-12 1:07 ` David S. Miller
2002-02-12 1:21 ` David Mosberger
2002-02-12 1:32 ` David S. Miller
2002-02-12 1:36 ` David Mosberger
2002-02-12 1:41 ` David S. Miller
2002-02-12 1:53 ` David Mosberger
2002-02-12 2:22 ` David S. Miller
2002-02-12 2:30 ` David Mosberger
2002-02-12 2:36 ` David S. Miller
2002-02-12 2:46 ` David Mosberger
2002-02-12 2:51 ` David S. Miller
2002-02-12 3:01 ` David Mosberger
2002-02-12 3:04 ` David S. Miller
2002-02-12 3:18 ` David Mosberger
2002-02-12 3:23 ` David S. Miller
2002-02-12 3:32 ` David Mosberger
2002-02-12 3:42 ` David S. Miller
2002-02-12 4:16 ` David Mosberger
2002-02-12 4:21 ` David S. Miller
2002-02-12 4:33 ` David Mosberger
2002-02-12 5:26 ` Richard Henderson
2002-02-12 5:32 ` David S. Miller
2002-02-12 5:50 ` David Mosberger
2002-02-12 5:57 ` Richard Henderson
2002-02-13 11:18 ` Anton Blanchard
2002-02-12 17:14 ` Pavel Machek
2002-02-13 0:46 ` David S. Miller
2002-02-13 1:30 ` Roman Zippel
2002-02-12 9:12 ` Roman Zippel
2002-02-12 9:30 ` Jeff Garzik
2002-02-12 10:14 ` Roman Zippel
2002-02-12 13:21 ` David Howells
2002-02-12 19:15 ` David Mosberger
2002-02-12 19:38 ` David Howells
2002-02-12 2:49 ` Davide Libenzi
2002-02-12 0:01 ` Roman Zippel
2002-02-12 0:10 ` David Howells
2002-02-12 0:22 ` Roman Zippel
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=1013458767.6785.459.camel@phantasy \
--to=rml@tech9.net \
--cc=LINUX-KERNEL@vger.kernel.org \
--cc=achapkis@mail.dls.net \
/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.