From: Thomas Gleixner <tglx@linutronix.de>
To: george@mvista.com
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
dwalker@mvista.com,
"'high-res-timers-discourse@lists.sourceforge.net'"
<high-res-timers-discourse@lists.sourceforge.net>,
john stultz <johnstul@us.ibm.com>
Subject: Re: 2.6.13-rt6, ktimer subsystem
Date: Fri, 16 Sep 2005 01:20:31 +0200 [thread overview]
Message-ID: <1126826431.6509.546.camel@tglx.tec.linutronix.de> (raw)
In-Reply-To: <4329FDF7.7080300@mvista.com>
On Thu, 2005-09-15 at 16:04 -0700, George Anzinger wrote:
> Possibly your involvement was that short. I rather doubt the code was
> written that quickly... I first found out about it on the 12th from the
> rt5 patch you posted about 2pm. Was there an earlier email?
The first sketch of ktimers was written in less than a day. Some
cleanups and the integration into -RT took not longer than 3-4 days.
tglx
next prev parent reply other threads:[~2005-09-15 23:20 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 10:00 2.6.13-rt6, ktimer subsystem Ingo Molnar
2005-09-13 19:59 ` Lee Revell
2005-09-13 20:06 ` Lee Revell
2005-09-13 20:10 ` Ingo Molnar
2005-09-13 20:36 ` Lee Revell
2005-09-15 7:55 ` Ingo Molnar
2005-09-15 11:37 ` Ingo Molnar
2005-09-14 15:56 ` Darren Hart
2005-09-14 22:09 ` Darren Hart
2005-09-14 19:38 ` George Anzinger
2005-09-15 2:25 ` Thomas Gleixner
2005-09-15 22:35 ` George Anzinger
2005-09-15 22:53 ` Thomas Gleixner
2005-09-15 23:10 ` George Anzinger
2005-09-15 23:09 ` Daniel Walker
2005-09-16 0:08 ` George Anzinger
2005-09-15 9:20 ` Ingo Molnar
2005-09-15 23:04 ` George Anzinger
2005-09-15 23:20 ` Thomas Gleixner [this message]
2005-09-15 9:43 ` Roman Zippel
2005-09-26 7:02 ` 2.6.14-rc2-rt2 Ingo Molnar
2005-09-27 6:13 ` 2.6.14-rc2-rt2 Eran Mann
2005-09-27 10:33 ` 2.6.14-rc2-rt2 Ingo Molnar
2005-09-27 16:59 ` 2.6.14-rc2-rt2 Fernando Lopez-Lezcano
2005-09-27 22:15 ` 2.6.14-rc2-rt2 Thomas Gleixner
2005-09-27 23:11 ` 2.6.14-rc2-rt2 Fernando Lopez-Lezcano
2005-09-27 23:10 ` 2.6.14-rc2-rt2 Daniel Walker
2005-09-28 3:04 ` 2.6.14-rc2-rt2 Fernando Lopez-Lezcano
2005-09-28 9:48 ` 2.6.14-rc2-rt2 Ingo Molnar
2005-09-28 16:34 ` 2.6.14-rc2-rt2 Fernando Lopez-Lezcano
2005-09-29 9:07 ` 2.6.14-rc2-rt2 Eran Mann
2005-09-28 9:10 ` 2.6.14-rc2-rt2 Peter Zijlstra
2005-09-29 16:45 ` 2.6.14-rc2-rt2 Badari Pulavarty
2005-09-30 10:58 ` 2.6.14-rc2-rt2 Ingo Molnar
2005-10-02 15:18 ` 2.6.14-rc3-rt1 Ingo Molnar
2005-10-02 15:42 ` 2.6.14-rc3-rt1 Mark Knecht
2005-10-02 19:25 ` 2.6.14-rc3-rt1 Mark Knecht
2005-10-06 17:13 ` 2.6.14-rc3-rt1 Steven Rostedt
2005-10-07 11:09 ` [patch] pcmcia-shutdown-fix.patch Ingo Molnar
2005-10-07 19:17 ` Russell King
2005-10-07 19:46 ` Steven Rostedt
2005-10-10 15:13 ` Steven Rostedt
2005-10-10 15:37 ` Steven Rostedt
2005-10-02 20:51 ` 2.6.14-rc3-rt1 Felix Oxley
2005-10-02 21:55 ` 2.6.14-rc3-rt1 Felix Oxley
2005-10-03 6:33 ` 2.6.14-rc3-rt1 Ingo Molnar
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=1126826431.6509.546.camel@tglx.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=dwalker@mvista.com \
--cc=george@mvista.com \
--cc=high-res-timers-discourse@lists.sourceforge.net \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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).