From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] davinci: Implement sched_clock()
Date: Fri, 08 Oct 2010 11:17:44 -0700 [thread overview]
Message-ID: <87mxqoy2ev.fsf@deeprootsystems.com> (raw)
In-Reply-To: <4CAEE9DA.1020900@mvista.com> (Sergei Shtylyov's message of "Fri, 08 Oct 2010 13:52:26 +0400")
Sergei Shtylyov <sshtylyov@mvista.com> writes:
> Hello.
>
> On 07-10-2010 21:12, Kevin Hilman wrote:
>
>>> Overwrite the default implementation of sched_clock that is based on
>>> jiffies by something more precise. This improves timestamps in ftrace.
>>> Implementation is copied from OMAP platform code.
>
>>> Signed-off-by: Andreas Gaeer<Andreas.Gaer@baslerweb.com>
>
>> Thanks, applying to davinci git.
>
>> Will queue for 2.6.38 (it's a bit too late for 2.6.37 as Linus only
>> wants real regression fixes after -rc6.)
>
> Did you mean 2.6.37 and 2.6.36 respecitvely?
Nope.
IOW, for the upcoming merge window (2.6.37), Linus does not want to see
new features done after 2.6.36-rc6. He wants to sure that by the time
the merge window opens, that things have received some testing and
validation, particularily in linux-next.
This means, that most maintainers (myself included) will not be taking
patches/features for 2.6.N merge window after 2.6.(N-1)-rc6 is released,
unless they are regression fixes.
Kevin
prev parent reply other threads:[~2010-10-08 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 8:38 [PATCH] davinci: Implement sched_clock() Andreas.Gaer at baslerweb.com
2010-10-07 17:12 ` Kevin Hilman
2010-10-08 9:52 ` Sergei Shtylyov
2010-10-08 18:17 ` Kevin Hilman [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=87mxqoy2ev.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).