From: john stultz <johnstul@us.ibm.com>
To: akataria@vmware.com
Cc: LKML <linux-kernel@vger.kernel.org>,
"jacob.jun.pan@intel.com" <jacob.jun.pan@intel.com>,
Glauber Costa <glommer@redhat.com>,
Dimitri Sivanich <sivanich@sgi.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Jeremy Fitzhardinge <jeremy@xensource.com>,
Chris McDermott <lcm@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 1/7] x86: Convert remaining clocksources to clocksource_register_hz/khz
Date: Thu, 21 Oct 2010 12:39:34 -0700 [thread overview]
Message-ID: <1287689974.4059.0.camel@localhost.localdomain> (raw)
In-Reply-To: <1287688604.27008.16.camel@ank32.eng.vmware.com>
On Thu, 2010-10-21 at 12:16 -0700, Alok Kataria wrote:
> Hi John,
>
> vmiclock_32.c doesn't exist anymore in tip and pretty soon should
> disappear from mainline too.
Ah. Thanks for the heads up!
-john
prev parent reply other threads:[~2010-10-21 19:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 23:44 [PATCH 0/7] clocksource_register_khz/hz cleanups(for 2.6.37?) John Stultz
2010-10-20 23:44 ` [PATCH 1/7] x86: Convert remaining clocksources to clocksource_register_hz/khz John Stultz
2010-10-20 23:44 ` [PATCH 2/7] sh: convert to clocksource_register_hz John Stultz
2010-10-20 23:44 ` [PATCH 3/7] ia64: convert to clocksource_register_hz/khz John Stultz
2010-10-20 23:44 ` [PATCH 4/7] sparc: " John Stultz
2010-10-20 23:44 ` [PATCH 5/7] avr32: Convert to clocksource_register_hz John Stultz
2010-10-20 23:44 ` [PATCH 6/7] mips: convert to clocksource_register_hz/khz John Stultz
2010-10-20 23:44 ` [PATCH 7/7] blackfin: convert to clocksource_register_hz John Stultz
2010-10-21 8:33 ` [PATCH 4/7] sparc: convert to clocksource_register_hz/khz David Miller
2010-10-21 19:16 ` [PATCH 1/7] x86: Convert remaining clocksources " Alok Kataria
2010-10-21 19:39 ` john stultz [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=1287689974.4059.0.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=akataria@vmware.com \
--cc=glommer@redhat.com \
--cc=jacob.jun.pan@intel.com \
--cc=jeremy@xensource.com \
--cc=lcm@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sivanich@sgi.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome