From: tom_gall@vnet.ibm.com
To: linuxppc-dev@lists.linuxppc.org
Subject: 2.4.0-test1 linux/sched.h
Date: Wed, 14 Jun 2000 13:43:04 +0000 [thread overview]
Message-ID: <39478BE8.3B6E6157@vnet.ibm.com> (raw)
Anyone notice that on
2.4.0-test1-ac18 that sched.h was changed to remove
#define PF_PTRACED 0x00000010
#define PF_TRACESYS 0x00000020
I need both of these systems to get a successful zImage built for my Power3 box.
Anyone know why there were removed, do we really really need this or should
dependancies on these symbols go?
Regards,
Tom
--
Tom Gall - PowerPC Linux Team "Where's the ka-boom? There was
Linux Technology Center supposed to be an earth
(w) tom_gall@vnet.ibm.com shattering ka-boom!"
(w) 507-253-4558 -- Marvin Martian
(h) tgall@uswest.net
http://oss.software.ibm.com/developerworks/opensource/linux
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-06-14 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-14 13:43 tom_gall [this message]
2000-06-19 2:26 ` 2.4.0-test1 linux/sched.h Paul Mackerras
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=39478BE8.3B6E6157@vnet.ibm.com \
--to=tom_gall@vnet.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).