All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Helsley <matthltc@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: john stultz <johnstul@us.ibm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Shailabh Nagar <nagar@watson.ibm.com>,
	Christoph Lameter <clameter@engr.sgi.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Jay Lan <jlan@sgi.com>, George Anzinger <george@mvista.com>
Subject: [PATCH 000/003] Remove getnstimestamp()
Date: Wed, 14 Dec 2005 20:29:46 -0800	[thread overview]
Message-ID: <1134620987.7372.35.camel@stark> (raw)

	This series removes the getnstimestamp() function from kernel/time.c in
favor of kernel/hrtimer.c's ktime_get_ts() function which currently does
exactly the same thing: retrieves a high-resolution (ns) timespec
structure and performs the wall_to_monotonic adjustment.

	As Jay Lan suggested I was going to replace calls to getnstimestamp()
with do_posix_clock_monotonic_gettime() but the hrtimer patches switched
that to a macro. ktime_get_ts() is shorter and avoids unnecessary
association with posix timers (though it does not emphasize monotonicity
or resolution).

The series:

001/003 export-ktime_get_ts.patch
	Exports ktime_get_ts()

002/003 proc-events-use-ktime-for-timestamp.patch
	Switches the only user of getnstimestamp() to ktime_get_ts()

003/003 rm-getnstimestamp.patch
	Remove getnstimestamp() from kernel/time.c


Thanks,
	-Matt Helsley



             reply	other threads:[~2005-12-15  4:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-15  4:29 Matt Helsley [this message]
2005-12-15  4:32 ` [PATCH 001/003] Export ktime_get_ts() Matt Helsley
2005-12-15  4:35 ` [PATCH 002/003] Switch getnstimestamp() calls to ktime_get_ts() Matt Helsley
2005-12-15  4:36 ` [PATCH 003/003] Remove getnstimestamp() Matt Helsley

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=1134620987.7372.35.camel@stark \
    --to=matthltc@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=clameter@engr.sgi.com \
    --cc=george@mvista.com \
    --cc=jlan@sgi.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nagar@watson.ibm.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 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.