From: Thomas Gleixner <tglx@linutronix.de>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] itimers: periodic timers fixes
Date: Thu, 14 May 2009 15:54:56 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0905141554080.3561@localhost.localdomain> (raw)
In-Reply-To: <20090514153908.0e689f70@dhcp-lab-109.englab.brq.redhat.com>
On Thu, 14 May 2009, Stanislaw Gruszka wrote:
> On Tue, 12 May 2009 23:11:57 +0200 (CEST)
> Thomas Gleixner <tglx@linutronix.de> wrote:
>
> > On Wed, 15 Apr 2009, Ingo Molnar wrote:
> > > > Could the patches be merged and possible other work done in later
> > > > time? Or perhaps I should rework on them?
> > >
> > > It's up to Thomas - but they certainly looked good to me.
> >
> > Huch, did I inherit the cputimers horror as a gratification for
> > touching kernel/*timer* at some point ?
> >
> > Seriously, give me a day or two to have a close look. I'm fighting
> > with a set of other timer related patches which I have delayed long
> > enough already.
>
> Thomas is your timers work accessible somewhere? I'm planing to do more
> changes in posix timers area and don't want to duplicate your work.
I did not touch posix timers and I'm not planing to do so.
Thanks,
tglx
prev parent reply other threads:[~2009-05-14 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 12:11 Stanislaw Gruszka
2009-04-02 16:57 ` Ingo Molnar
2009-04-03 12:59 ` Stanislaw Gruszka
2009-04-15 12:22 ` Stanislaw Gruszka
2009-04-15 13:59 ` Ingo Molnar
2009-04-15 14:02 ` Oleg Nesterov
2009-05-12 21:11 ` Thomas Gleixner
2009-05-13 12:55 ` Ingo Molnar
2009-05-14 13:39 ` Stanislaw Gruszka
2009-05-14 13:54 ` 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=alpine.LFD.2.00.0905141554080.3561@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=sgruszka@redhat.com \
/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
Powered by JetHome