From: Tom Gall <tom_gall@vnet.ibm.com>
To: paulus@samba.org, linuxppc-dev@lists.linuxppc.org
Subject: _devel still b0rked
Date: Mon, 17 Sep 2001 23:03:51 +0000 [thread overview]
Message-ID: <3BA68157.837572BF@vnet.ibm.com> (raw)
Hi Paul,
Well I pulled the latest linuxppc_2_4_devel sources today for my G3 and things
are still b0rked. Can't do a complete kernel build without taking random
segfaults.
Did you have a chance to look into things based on the config I set you last
week?
Thanks,
Tom
PS Perhaps you want an accout on the machine so you can directly track it down?
--
Tom Gall - PPC64 Code Monkey "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@rochcivictheatre.org
http://www.ibm.com/linux/ltc/projects/ppc
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-09-17 23:03 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=3BA68157.837572BF@vnet.ibm.com \
--to=tom_gall@vnet.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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).