From: "Mikael Starvik" <mikael.starvik@axis.com>
To: "'Arjan van de Ven'" <arjan@infradead.org>,
"Mikael Starvik" <mikael.starvik@axis.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Accessing monotonic clock from modules
Date: Thu, 2 Jun 2005 12:57:51 +0200 [thread overview]
Message-ID: <BFECAF9E178F144FAEF2BF4CE739C66801B7645D@exmail1.se.axis.com> (raw)
In-Reply-To: <BFECAF9E178F144FAEF2BF4CE739C66802FA37AC@exmail1.se.axis.com>
>how about making this a _GPL export?
Yes
>also... when are you going to get this module merged?
Do we really want modules for all kind of exotic hardware only used by one
company in the kernel tree? In this case we are the only user of this module
since we make the HW ourself and doesn't resell it. So it's my headache if
any API or similar is changed.
>And if we are going to make it an official interface, does it have to be
>called "do_posix_clock_monotonic_gettime" ? Perhaps a more
>export-friendly name?
Sure. Any suggestions welcome.
/Mikael
-----Original Message-----
From: Arjan van de Ven [mailto:arjan@infradead.org]
Sent: Thursday, June 02, 2005 9:30 AM
To: Mikael Starvik
Cc: linux-kernel@vger.kernel.org
Subject: Re: Accessing monotonic clock from modules
On Thu, 2005-06-02 at 08:36 +0200, Mikael Starvik wrote:
> We would like to get the posix monotonic clock from a loadable module.
> Would a patch to make do_posix_clock_monotonic_gettime exported ok or
> should we do it in some other way?
>
> /Mikael
also... when are you going to get this module merged?
(exporting things without the module going into kernel.org shouldn't be
done imo... it makes it harder to change internals and causes overhead
for all kernel users)
next parent reply other threads:[~2005-06-02 10:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BFECAF9E178F144FAEF2BF4CE739C66802FA37AC@exmail1.se.axis.com>
2005-06-02 10:57 ` Mikael Starvik [this message]
2005-06-02 11:15 ` Arjan van de Ven
[not found] <BFECAF9E178F144FAEF2BF4CE739C66802FA3913@exmail1.se.axis.com>
2005-06-02 12:40 ` Mikael Starvik
2005-06-02 6:36 Mikael Starvik
2005-06-02 7:29 ` Arjan van de Ven
2005-06-02 7:30 ` Arjan van de Ven
2005-06-02 7:40 ` Robert Love
2005-06-02 7:48 ` Arjan van de Ven
2005-06-02 7:52 ` Robert Love
2005-06-02 7:56 ` Arjan van de Ven
2005-06-02 13:46 ` Chris Friesen
2005-06-02 13:48 ` Arjan van de Ven
2005-06-02 14:21 ` Chris Friesen
2005-06-04 3:27 ` Lee Revell
2005-06-04 21:48 ` Lee Revell
2005-06-03 0:14 ` Gerald Britton
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=BFECAF9E178F144FAEF2BF4CE739C66801B7645D@exmail1.se.axis.com \
--to=mikael.starvik@axis.com \
--cc=arjan@infradead.org \
--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
all inboxes | Powered by JetHome®