From: Zhang Rui <rui.zhang@intel.com>
To: Arnd Bergmann <arnd@arndb.de>,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
Deepa Dinamani <deepa.kernel@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] time: export nsec_to_clock_t
Date: Thu, 29 Mar 2018 22:58:10 +0800 [thread overview]
Message-ID: <1522335490.2964.2.camel@intel.com> (raw)
In-Reply-To: <20180328141205.2954245-1-arnd@arndb.de>
On 三, 2018-03-28 at 16:11 +0200, Arnd Bergmann wrote:
> nsec_to_clock_t was traditionally used only in the core kernel, now
> we
> have a sysfs file that needs it from a loadable module, causing a
> link-time error:
>
> ERROR: "nsec_to_clock_t" [drivers/thermal/thermal_sys.ko] undefined!
>
> This exports the function the same way that we do for related
> interfaces.
>
> Fixes: 96cea33badc5 ("thermal: Add cooling device's statistics in
> sysfs")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Thanks for the fix.
can I take this patch through thermal tree?
thanks,
rui
> ---
> kernel/time/time.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/time/time.c b/kernel/time/time.c
> index 6fa99213fc72..97a262531f68 100644
> --- a/kernel/time/time.c
> +++ b/kernel/time/time.c
> @@ -768,6 +768,7 @@ u64 nsec_to_clock_t(u64 x)
> return div_u64(x * 9, (9ull * NSEC_PER_SEC + (USER_HZ / 2))
> / USER_HZ);
> #endif
> }
> +EXPORT_SYMBOL(nsec_to_clock_t);
>
> u64 jiffies64_to_nsecs(u64 j)
> {
next prev parent reply other threads:[~2018-03-29 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 14:11 [PATCH] time: export nsec_to_clock_t Arnd Bergmann
2018-03-29 14:58 ` Zhang Rui [this message]
2018-03-29 19:11 ` Thomas Gleixner
2018-04-02 10:25 ` Viresh Kumar
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=1522335490.2964.2.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
--cc=viro@zeniv.linux.org.uk \
/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.