From: Nicolai Stange <nicstange@gmail.com>
To: Nicolai Stange <nicstange@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, John Stultz <john.stultz@linaro.org>,
Borislav Petkov <bp@suse.de>, Paolo Bonzini <pbonzini@redhat.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>,
"Peter Zijlstra \(Intel\)" <peterz@infradead.org>,
"Christopher S. Hall" <christopher.s.hall@intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Suresh Siddha <suresh.b.siddha@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] avoid double timer interrupt with nohz and Intel TSC
Date: Sun, 10 Jul 2016 21:32:33 +0200 [thread overview]
Message-ID: <87a8hps2zy.fsf@gmail.com> (raw)
In-Reply-To: <20160710122345.13061-1-nicstange@gmail.com> (Nicolai Stange's message of "Sun, 10 Jul 2016 14:23:41 +0200")
Please drop in favour of v2.
Thanks,
Nicolai
prev parent reply other threads:[~2016-07-10 19:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 12:23 [PATCH 0/4] avoid double timer interrupt with nohz and Intel TSC Nicolai Stange
2016-07-10 12:23 ` [PATCH 1/4] arch, x86, tsc deadline clockevent dev: reduce frequency roundoff error Nicolai Stange
2016-07-10 12:23 ` [PATCH 2/4] arch, x86, tsc deadline clockevent dev: reduce TSC_DIVISOR to 2 Nicolai Stange
2016-07-10 12:23 ` [PATCH 3/4] arch, x86, tsc: inform TSC deadline clockevent device about recalibration Nicolai Stange
2016-07-10 12:46 ` kbuild test robot
2016-07-10 12:23 ` [PATCH 4/4] kernel/time/clockevents: compensate for monotonic clock's dynamic frequency Nicolai Stange
2016-07-10 13:20 ` kbuild test robot
2016-07-10 13:56 ` kbuild test robot
2016-07-10 14:17 ` kbuild test robot
2016-07-10 19:32 ` Nicolai Stange [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=87a8hps2zy.fsf@gmail.com \
--to=nicstange@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=bp@suse.de \
--cc=christopher.s.hall@intel.com \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=hpa@zytor.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
--cc=x86@kernel.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