From: Ingo Molnar <mingo@elte.hu>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH 00/12] hrtimer patches
Date: Tue, 14 Feb 2006 12:09:47 +0100 [thread overview]
Message-ID: <20060214110947.GA25341@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.61.0602141057320.30994@scrub.home>
* Roman Zippel <zippel@linux-m68k.org> wrote:
> Here is new version of the hrtimer patches sorted by priority. I
> dropped the remaining time patch, the const patch doesn't produce a
> larger kernel with gcc3 and I also added the acks so far. I consider
> the first four patches the most important and the remaining patches
> simple enough, that I think they're still 2.6.16 material.
i only consider the first two patches to be 2.6.16 material. The other
patches avoid a ->get_time() call per timer interrupt - that's noise at
most ...
Ingo
next prev parent reply other threads:[~2006-02-14 11:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 10:10 [PATCH 00/12] hrtimer patches Roman Zippel
2006-02-14 11:09 ` Ingo Molnar [this message]
2006-02-14 11:34 ` Roman Zippel
2006-02-14 12:32 ` Ingo Molnar
2006-02-14 12:59 ` Roman Zippel
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=20060214110947.GA25341@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zippel@linux-m68k.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