From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: restore bogomips information in /proc/cpuinfo
Date: Thu, 26 Nov 2015 10:23:05 +0000 [thread overview]
Message-ID: <1448533385.2817.19.camel@linaro.org> (raw)
In-Reply-To: <alpine.LFD.2.20.1511251303220.22569@knanqh.ubzr>
On Wed, 2015-11-25 at 13:09 -0500, Nicolas Pitre wrote:
> But CPU MHz, when available, has the merit of not being open to
> interpretation.
Current MHz, maximum MHz or 'turbo' MHz? ;-)
--
Tixy
WARNING: multiple messages have this Message-ID (diff)
From: "Jon Medhurst (Tixy)" <tixy@linaro.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: "Shi, Yang" <yang.shi@linaro.org>,
linaro-kernel@lists.linaro.org, Jon Masters <jcm@jonmasters.org>,
Catalin.Marinas@arm.com, Will.Deacon@arm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: restore bogomips information in /proc/cpuinfo
Date: Thu, 26 Nov 2015 10:23:05 +0000 [thread overview]
Message-ID: <1448533385.2817.19.camel@linaro.org> (raw)
In-Reply-To: <alpine.LFD.2.20.1511251303220.22569@knanqh.ubzr>
On Wed, 2015-11-25 at 13:09 -0500, Nicolas Pitre wrote:
> But CPU MHz, when available, has the merit of not being open to
> interpretation.
Current MHz, maximum MHz or 'turbo' MHz? ;-)
--
Tixy
next prev parent reply other threads:[~2015-11-26 10:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 18:15 [PATCH] arm64: restore bogomips information in /proc/cpuinfo Yang Shi
2015-11-18 18:15 ` Yang Shi
2015-11-18 18:47 ` Will Deacon
2015-11-18 18:47 ` Will Deacon
2015-11-18 18:54 ` Shi, Yang
2015-11-18 18:54 ` Shi, Yang
2015-11-18 21:55 ` Nicolas Pitre
2015-11-18 21:55 ` Nicolas Pitre
2015-11-19 12:20 ` Will Deacon
2015-11-19 12:20 ` Will Deacon
2015-11-25 5:45 ` Jon Masters
2015-11-25 5:45 ` Jon Masters
2015-11-25 11:52 ` Catalin Marinas
2015-11-25 11:52 ` Catalin Marinas
2015-11-25 12:00 ` Russell King - ARM Linux
2015-11-25 12:00 ` Russell King - ARM Linux
2015-11-25 12:36 ` Riku Voipio
2015-11-25 12:36 ` Riku Voipio
2015-11-25 15:16 ` Nicolas Pitre
2015-11-25 15:16 ` Nicolas Pitre
2015-11-25 17:32 ` Shi, Yang
2015-11-25 17:32 ` Shi, Yang
2015-11-25 18:09 ` Nicolas Pitre
2015-11-25 18:09 ` Nicolas Pitre
2015-11-26 10:23 ` Jon Medhurst (Tixy) [this message]
2015-11-26 10:23 ` Jon Medhurst (Tixy)
-- strict thread matches above, loose matches on Subject: below --
2016-01-27 12:14 Will Deacon
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=1448533385.2817.19.camel@linaro.org \
--to=tixy@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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.