From: Ingo Molnar <mingo@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com,
peterz@infradead.org, bp@alien8.de, paulmck@linux.vnet.ibm.com,
rostedt@goodmis.org, jbohac@suse.cz, tglx@linutronix.de,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:timers/urgent] nohz: Prevent broadcast source from stealing full dynticks timekeeping duty
Date: Fri, 31 May 2013 14:50:18 +0200 [thread overview]
Message-ID: <20130531125018.GA8791@gmail.com> (raw)
In-Reply-To: <20130531124930.GB5932@somewhere>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> On Fri, May 31, 2013 at 05:43:25AM -0700, tip-bot for Frederic Weisbecker wrote:
> > Commit-ID: 81e747d2ccfa9faa2b10507dca9d4b42796c561e
> > Gitweb: http://git.kernel.org/tip/81e747d2ccfa9faa2b10507dca9d4b42796c561e
> > Author: Frederic Weisbecker <fweisbec@gmail.com>
> > AuthorDate: Tue, 28 May 2013 15:29:03 +0200
> > Committer: Ingo Molnar <mingo@kernel.org>
> > CommitDate: Fri, 31 May 2013 11:33:36 +0200
> >
> > nohz: Prevent broadcast source from stealing full dynticks timekeeping duty
>
> Hi Ingo,
>
> Sorry I made several versions of posting and pull requests and it probably
> became confusing.
>
> This patch was dropped in the latest version (nohz:timers/urgent-for-tip-v2)
> and got replaced by 02afeab42700a66a52aaedd21bcef0cd1994f715
> ("tick: Remove useless timekeeping duty attribution to broadcast source").
>
> I hope you can still swap these.
>
> The other commits are fine.
I zapped 81e747d - please double check it: does tip:timers/urgent look
good to you now?
Thanks,
Ingo
next prev parent reply other threads:[~2013-05-31 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-81e747d2ccfa9faa2b10507dca9d4b42796c561e@git.kernel.org>
2013-05-31 12:49 ` [tip:timers/urgent] nohz: Prevent broadcast source from stealing full dynticks timekeeping duty Frederic Weisbecker
2013-05-31 12:50 ` Ingo Molnar [this message]
2013-05-31 12:57 ` Frederic Weisbecker
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=20130531125018.GA8791@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jbohac@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.