From: Stas Sergeev <stsp@aknet.ru>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] export hrtimer_forward
Date: Thu, 03 May 2007 23:10:02 +0400 [thread overview]
Message-ID: <463A338A.2010909@aknet.ru> (raw)
In-Reply-To: <1178218674.24217.14.camel@twins>
Hello.
Peter Zijlstra wrote:
>> It seems hrtimer_forward was forgotten to
>> export - other symbols of the hrtimers API
> Are there actual in-tree users of this symbol? Without we usually leave
> the symbol unexported, this saves some space.
Do you mean it was really left intentional?
Unbeleivable! But why the other parts of a
hrtimer API are exported nevertheless, and
only this particular function not?
As for the users - I am porting my pcsp driver to
it and I need that function.
It is not exactly in-tree stuff, but it was
in an ALSA tree for years already, so it is a
close one.
next prev parent reply other threads:[~2007-05-03 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 17:57 [patch] export hrtimer_forward Stas Sergeev
2007-05-03 18:57 ` Peter Zijlstra
2007-05-03 19:10 ` Stas Sergeev [this message]
2007-05-03 23:58 ` Andrew Morton
2007-05-04 21:08 ` Thomas Gleixner
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=463A338A.2010909@aknet.ru \
--to=stsp@aknet.ru \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.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