From: Dmitry Nezhevenko <dion@inhex.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
Shaohua Li <shaohua.li@intel.com>,
"Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
Subject: Re: [patch 0/6] final clockevents/hpet fixes
Date: Thu, 4 Sep 2008 02:00:03 +0300 [thread overview]
Message-ID: <20080903230003.GA1958@laptop.local> (raw)
In-Reply-To: <20080903212735.713411776@linutronix.de>
On Wed, Sep 03, 2008 at 09:36:25PM -0000, Thomas Gleixner wrote:
> This is the final version of the various clockevents fixes, which I will
> send to Linus. Can you please give it a try on your machines, so we can
> be sure that I did not mess up anything again.
>
Applied full patchset on top of 2.6.27-rc5. Works great on my affected system.
Tested-by: Dmitry Nezhevenko <dion@inhex.net>
--
WBR, Dmitry
next prev parent reply other threads:[~2008-09-03 23:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 21:36 [patch 0/6] final clockevents/hpet fixes Thomas Gleixner
2008-09-03 21:36 ` [patch 1/6] clockevents: Prevent clockevent event_handler ending up handler_noop Thomas Gleixner
2008-09-03 21:36 ` [patch 2/6] clockevents: prevent endless loop in periodic broadcast handler Thomas Gleixner
2008-09-03 21:37 ` [patch 3/6] clockevents: enforce reprogram in oneshot setup Thomas Gleixner
2008-09-03 21:37 ` [patch 4/6] clockevents: prevent multiple init/shutdown Thomas Gleixner
2008-09-03 21:37 ` [patch 5/6] clockevents: prevent endless loop lockup Thomas Gleixner
2008-09-03 21:37 ` [patch 6/6] HPET: make minimum reprogramming delta useful Thomas Gleixner
2008-09-03 23:00 ` Dmitry Nezhevenko [this message]
2008-09-03 23:04 ` [patch 0/6] final clockevents/hpet fixes Thomas Gleixner
2008-09-03 23:27 ` Dmitry Nezhevenko
2008-09-04 18:33 ` Luiz Fernando N. Capitulino
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=20080903230003.GA1958@laptop.local \
--to=dion@inhex.net \
--cc=lcapitulino@mandriva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shaohua.li@intel.com \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.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