From: Ingo Molnar <mingo@elte.hu>
To: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Arjan van de Ven <arjan@linux.intel.com>,
linux-fsdevel@vger.kernel.org,
Steven Rostedt <srostedt@redhat.com>
Subject: Re: [PATCH 1/2] hrtimer: export ktime_add_safe
Date: Mon, 1 Jun 2009 21:56:00 +0200 [thread overview]
Message-ID: <20090601195600.GF29610@elte.hu> (raw)
In-Reply-To: <20090529150938.8912.3443.sendpatchset@localhost.localdomain>
* Artem Bityutskiy <Artem.Bityutskiy@nokia.com> wrote:
> From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> Subject: [PATCH 1/2] hrtimer: export ktime_add_safe
>
> We want to use hrtimers in UBIFS (for write-buffer write-back timer).
> We need the 'hrtimer_set_expires_range_ns()', which is an in-line
> function which uses 'ktime_add_safe()'.
>
> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> ---
> kernel/hrtimer.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
> index cb8a15c..18f6906 100644
> --- a/kernel/hrtimer.c
> +++ b/kernel/hrtimer.c
> @@ -332,6 +332,8 @@ ktime_t ktime_add_safe(const ktime_t lhs, const ktime_t rhs)
> return res;
> }
>
> +EXPORT_SYMBOL_GPL(ktime_add_safe);
> +
Feel free to queue this up in your tree - it's trivial enough.
Acked-by: Ingo Molnar <mingo@elte.hu>
Ingo
next prev parent reply other threads:[~2009-06-01 19:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 15:09 [PATCH 0/2] Use hrtimers in UBIFS Artem Bityutskiy
2009-05-29 15:09 ` [PATCH 1/2] hrtimer: export ktime_add_safe Artem Bityutskiy
2009-06-01 19:56 ` Ingo Molnar [this message]
2009-06-02 5:39 ` Artem Bityutskiy
2009-06-02 5:39 ` Artem Bityutskiy
2009-05-29 15:09 ` [PATCH 2/2] UBIFS: start using hrtimers Artem Bityutskiy
2009-05-29 13:32 ` Peter Zijlstra
2009-05-29 13:58 ` Artem Bityutskiy
2009-05-29 13:58 ` Artem Bityutskiy
2009-05-29 14:00 ` Artem Bityutskiy
2009-05-29 14:00 ` Artem Bityutskiy
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=20090601195600.GF29610@elte.hu \
--to=mingo@elte.hu \
--cc=Artem.Bityutskiy@nokia.com \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
/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.