From: Ingo Molnar <mingo@kernel.org>
To: viresh kumar <viresh.kumar@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
Steven Miao <realmz6@gmail.com>,
shashim@codeaurora.org
Subject: Re: [PATCH 1/2] timer: Avoid waking up an idle-core by migrate running timer
Date: Fri, 17 Apr 2015 10:32:47 +0200 [thread overview]
Message-ID: <20150417083247.GA12278@gmail.com> (raw)
In-Reply-To: <5530C086.2020700@linaro.org>
* viresh kumar <viresh.kumar@linaro.org> wrote:
> + /*
> + * Timer handler re-armed timer and we didn't wanted to add that
> + * on a idle local CPU. Its handler has finished now, lets
> + * enqueue it again.
> + */
That single comment has 5 grammatical errors!
Thanks,
Ingo
next prev parent reply other threads:[~2015-04-17 8:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 6:55 [PATCH 0/2] timer: Migrate running timers Viresh Kumar
2015-03-31 6:55 ` [PATCH 1/2] timer: Avoid waking up an idle-core by migrate running timer Viresh Kumar
2015-03-31 14:53 ` Peter Zijlstra
2015-04-14 23:13 ` Thomas Gleixner
2015-04-17 8:12 ` viresh kumar
2015-04-17 8:32 ` Ingo Molnar [this message]
2015-04-21 21:32 ` Thomas Gleixner
2015-04-21 21:54 ` Eric Dumazet
2015-04-22 15:29 ` Peter Zijlstra
2015-04-22 16:02 ` Eric Dumazet
2015-04-22 18:56 ` Thomas Gleixner
2015-04-22 19:59 ` Eric Dumazet
2015-04-22 21:56 ` Thomas Gleixner
2015-04-23 6:57 ` Eric Dumazet
2015-04-23 12:45 ` Thomas Gleixner
2015-04-25 18:37 ` Eric Dumazet
2015-05-05 13:00 ` Thomas Gleixner
2015-05-06 16:33 ` Eric Dumazet
2015-04-15 15:54 ` Thomas Gleixner
2015-03-31 6:55 ` [PATCH 2/2] timer: Replace base-> 'running_timer' with 'busy' Viresh Kumar
2015-03-31 15:01 ` [PATCH 0/2] timer: Migrate running timers Viresh Kumar
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=20150417083247.GA12278@gmail.com \
--to=mingo@kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=realmz6@gmail.com \
--cc=shashim@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.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 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.