public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Alok Kataria <akataria@vmware.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	the arch/x86 maintainers <x86@kernel.org>,
	Dan Hecht <dhecht@vmware.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 05/05] x86: Rename paravirtualized TSC functions
Date: Wed, 9 Jul 2008 08:13:36 +0200	[thread overview]
Message-ID: <20080709061336.GG9760@elte.hu> (raw)
In-Reply-To: <1214937816.20191.34.camel@promb-2n-dhcp368.eng.vmware.com>


* Alok Kataria <akataria@vmware.com> wrote:

> Rename the paravirtualized calculate_cpu_khz to calibrate_tsc. In all 
> cases, we actually calibrate_tsc and use that as the cpu_khz value.

thanks Alok, i've applied all 5 unification patches to tip/x86/core:

 Alok Kataria (5):
       x86: merge sched_clock handling
       x86: merge tsc calibration
       x86: merge the TSC cpu-freq code
       x86: merge tsc_init and clocksource code
       x86: rename paravirtualized TSC functions

they are looking good in testing so far.

	Ingo

  reply	other threads:[~2008-07-09  6:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 18:43 [PATCH 05/05] x86: Rename paravirtualized TSC functions Alok Kataria
2008-07-09  6:13 ` Ingo Molnar [this message]
2008-07-09  7:20   ` Yinghai Lu
2008-07-09 17:30     ` Alok Kataria
2008-07-09 17:38       ` Yinghai Lu
2008-07-10  7:22         ` Ingo Molnar
2008-07-10  7:34           ` Yinghai Lu
2008-07-10  7:50             ` Ingo Molnar
2008-07-10  8:04               ` Yinghai Lu
2008-07-10  8:11                 ` Yinghai Lu
2008-07-10 10:22                   ` Yinghai Lu
2008-07-10  8:12                 ` Ingo Molnar
2008-07-10 18:59                   ` Jeremy Fitzhardinge

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=20080709061336.GG9760@elte.hu \
    --to=mingo@elte.hu \
    --cc=akataria@vmware.com \
    --cc=dhecht@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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