From: Thunder from the hill <thunder@ngforever.de>
To: ultralinux@vger.kernel.org
Subject: arch/sparc(|64)/kernel/entry.S:do_fork_FIXME_NOW_RETURNS_TASK_STRUCT
Date: Wed, 22 May 2002 15:12:06 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-102208060920224@msgid-missing> (raw)
Hi,
I was looking out for a solution for the latest compile problems on
sparc(|64): in arch/sparc(|64)/kernel/entry.S we have a symbol named
do_fork_FIXME_NOW_RETURNS_TASK_STRUCT introduced by Rusty Russel, which of
course is undefined. It's in the sparc thread implementation as well as
in the sys_fork implementation on sparc64.
Any ideas what to do about that?
BTW, please make sure you carbon copy to me, for I'm on neither sparclinux
nor ultralinux.
Regards,
Thunder
--
Was it a black who passed along in the sand?
Was it a white who left his footprints?
Was it an african? An indian?
Sand says, 'twas human.
reply other threads:[~2002-05-22 15:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ultrasparc-102208060920224@msgid-missing \
--to=thunder@ngforever.de \
--cc=ultralinux@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).