From: Olaf Hering <olh@suse.de>
To: Arnd Bergmann <arnd.bergmann@de.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackeras <paulus@samba.org>
Subject: Re: [PATCH] remove bogomips from /proc/cpuinfo
Date: Mon, 31 Jul 2006 19:49:24 +0200 [thread overview]
Message-ID: <20060731174924.GA4273@suse.de> (raw)
In-Reply-To: <200607311946.18331.arnd.bergmann@de.ibm.com>
On Mon, Jul 31, Arnd Bergmann wrote:
> On Monday 31 July 2006 14:59, Olaf Hering wrote:
> > Remove bogomips from /proc/cpuinfo.
> > It is now really bogus since "timebase-frequency" is shown.
>
> Well, but it's still part of the ABI, right?
> How do you determine that there are no broken applications
> still relying on it?
Everything works on a G5, as example. Alpha doesnt have it either.
What pratical value had bogomips for an application?
next prev parent reply other threads:[~2006-07-31 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 12:59 [PATCH] remove bogomips from /proc/cpuinfo Olaf Hering
2006-07-31 17:46 ` Arnd Bergmann
2006-07-31 17:49 ` Olaf Hering [this message]
2006-07-31 18:17 ` Andreas Schwab
2006-07-31 18:57 ` Linas Vepstas
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=20060731174924.GA4273@suse.de \
--to=olh@suse.de \
--cc=arnd.bergmann@de.ibm.com \
--cc=linuxppc-dev@ozlabs.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 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.