linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Nicolas Pitre <nico@linaro.org>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"cov@codeaurora.org" <cov@codeaurora.org>,
	Marc Zyngier <Marc.Zyngier@arm.com>
Subject: Re: [PATCH v2 0/2] ARM: Remove any correlation between IPC and BogoMips value
Date: Fri, 21 Jun 2013 09:40:19 +0100	[thread overview]
Message-ID: <20130621084018.GB6983@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <alpine.LFD.2.03.1306201452330.18597@syhkavp.arg>

On Thu, Jun 20, 2013 at 07:54:21PM +0100, Nicolas Pitre wrote:
> On Thu, 20 Jun 2013, Will Deacon wrote:
> 
> > Hi all,
> > 
> > This is version two of the patches I originally posted here:
> > 
> >   http://lists.infradead.org/pipermail/linux-arm-kernel/2013-May/166728.html
> > 
> > Comments received there largely confirmed that it's not possible to choose
> > an `obviously bogus' value for BogoMIPs, so instead I've bitten the bullet
> > and removed the line altogether.
> > 
> > In the meantime, I've only had one complaint this month about BogoMIPs
> > being wrong, so perhaps the initial posting served some purpose without
> > even being merged!
> > 
> > Comments welcome,
> 
> Enthusiastic ACK for both patches.

Thanks Nicolas!

Will

  reply	other threads:[~2013-06-21  8:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 16:43 [PATCH v2 0/2] ARM: Remove any correlation between IPC and BogoMips value Will Deacon
2013-06-20 16:43 ` [PATCH v2 1/2] ARM: delay: don't bother reporting bogomips in /proc/cpuinfo Will Deacon
2013-06-20 16:43 ` [PATCH v2 2/2] init: calibrate: don't print out bogomips value on boot Will Deacon
2013-06-20 18:54 ` [PATCH v2 0/2] ARM: Remove any correlation between IPC and BogoMips value Nicolas Pitre
2013-06-21  8:40   ` Will Deacon [this message]
2013-06-21  9:47 ` Marc Zyngier

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=20130621084018.GB6983@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=Marc.Zyngier@arm.com \
    --cc=cov@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@linaro.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).