2007-05-03 18:28:33

by Stas Sergeev

[permalink] [raw]
Subject: [patch] export hrtimer_forward

Hello.

It seems hrtimer_forward was forgotten to
export - other symbols of the hrtimers API
are already exported.
Unless I am missing something, using the
hrtimers without that function is problematic.

Andrew, could you please apply?

Signed-off-by: <[email protected]>


Attachments:
exp_hrfwd.diff (262.00 B)

2007-05-03 18:57:59

by Peter Zijlstra

[permalink] [raw]
Subject: Re: [patch] export hrtimer_forward

On Thu, 2007-05-03 at 21:57 +0400, Stas Sergeev wrote:
> Hello.
>
> It seems hrtimer_forward was forgotten to
> export - other symbols of the hrtimers API
> are already exported.
> Unless I am missing something, using the
> hrtimers without that function is problematic.
>
> Andrew, could you please apply?

Are there actual in-tree users of this symbol? Without we usually leave
the symbol unexported, this saves some space.

2007-05-03 19:07:26

by Stas Sergeev

[permalink] [raw]
Subject: Re: [patch] export hrtimer_forward

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.

2007-05-03 23:58:39

by Andrew Morton

[permalink] [raw]
Subject: Re: [patch] export hrtimer_forward

On Thu, 03 May 2007 23:10:02 +0400
Stas Sergeev <[email protected]> wrote:

> 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?

It was probably an oversight - generally we take the position that all the
formal interface of a subsystem is exported to modules rather than a
piecemeal whichever-bits-kernel.org-happens-to-use-today approach.

Thomas, is hrtimer_forward() considered part of the hrtimer public API?
And are you OK with the patch?


> 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.

2007-05-04 21:06:58

by Thomas Gleixner

[permalink] [raw]
Subject: Re: [patch] export hrtimer_forward

On Thu, 2007-05-03 at 16:58 -0700, Andrew Morton wrote:
> It was probably an oversight - generally we take the position that all the
> formal interface of a subsystem is exported to modules rather than a
> piecemeal whichever-bits-kernel.org-happens-to-use-today approach.
>
> Thomas, is hrtimer_forward() considered part of the hrtimer public API?
> And are you OK with the patch?

Yes to both.

tglx