public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: mmc@maruska.dyndns.org (Michal Maruška)
To: linux-kernel@vger.kernel.org
Cc: george@mvista.com
Subject: [PATCH 2.6.15-rc7] clocks: export symbol do_posix_clock_monotonic_gettime
Date: Mon, 26 Dec 2005 23:20:22 +0100	[thread overview]
Message-ID: <m264pbo5zt.fsf@linux11.maruska.tin.it> (raw)

[-- Attachment #1: Type: text/plain, Size: 341 bytes --]


Getting access to monotonic time from modules is indispensable, for instance,
for modular evdev to timestamp input events with a useful time information.

(I have already provided patch for evdev (also this one) in my previous,
unanswered, post http://lkml.org/lkml/2005/10/6/92 )


Signed-off-by: Michal Maruska <mmc@maruska.dyndns.org> 


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: posix-timers.c.patch --]
[-- Type: text/x-patch, Size: 420 bytes --]

--- linux-2.6.15-rc7/kernel/posix-timers.c	2005-12-26 13:01:54.000000000 +0100
+++ linux-2.6.15-rc7.mmc/kernel/posix-timers.c	2005-12-26 22:59:11.883817855 +0100
@@ -1219,6 +1219,7 @@ int do_posix_clock_monotonic_gettime(str
 {
 	return do_posix_clock_monotonic_get(CLOCK_MONOTONIC, tp);
 }
+EXPORT_SYMBOL_GPL(do_posix_clock_monotonic_gettime);
 
 int do_posix_clock_nosettime(clockid_t clockid, struct timespec *tp)
 {

             reply	other threads:[~2005-12-26 22:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26 22:20 Michal Maruška [this message]
2005-12-27  7:52 ` [PATCH 2.6.15-rc7] clocks: export symbol do_posix_clock_monotonic_gettime Arjan van de Ven
2005-12-27 23:07   ` [PATCH 2.6.15-rc7] clocks: export symbol do_posix_clock_monotonic_gettime + input: monotonic timestamps for evdev Michal Maruška

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=m264pbo5zt.fsf@linux11.maruska.tin.it \
    --to=mmc@maruska.dyndns.org \
    --cc=george@mvista.com \
    --cc=linux-kernel@vger.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