From: benh@kernel.crashing.org
To: Robert E Brose II <bob@kunk.jriver.com>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: cat /proc/cpuinfo oops in 2.4.19-pre3-ben0
Date: Thu, 21 Mar 2002 00:35:08 +0100 [thread overview]
Message-ID: <20020320233508.18205@mailhost.mipsys.com> (raw)
In-Reply-To: <20020321023830.1777.qmail@kunk.jriver.com>
>Supermac S900 w/ 604e 233 and 256 megs ram. Worked fine in
>2.4.17-ben0
Thanks for the report, I think I know what's wrong, I'll push
a fix later today.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-03-20 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 2:38 cat /proc/cpuinfo oops in 2.4.19-pre3-ben0 Robert E Brose II
2002-03-20 23:35 ` benh [this message]
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=20020320233508.18205@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=bob@kunk.jriver.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 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.