From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stas Sergeev <stsp@aknet.ru>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] export hrtimer_forward
Date: Fri, 04 May 2007 23:08:36 +0200 [thread overview]
Message-ID: <1178312916.4471.0.camel@chaos> (raw)
In-Reply-To: <20070503165800.5b7cd3fd.akpm@linux-foundation.org>
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
prev parent reply other threads:[~2007-05-04 21:06 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
2007-05-03 23:58 ` Andrew Morton
2007-05-04 21:08 ` Thomas Gleixner [this message]
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=1178312916.4471.0.camel@chaos \
--to=tglx@linutronix.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stsp@aknet.ru \
/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