From: Ingo Molnar <mingo@kernel.org>
To: Len Brown <lenb@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/5] x86: remove idle notifier
Date: Fri, 18 Nov 2016 09:17:55 +0100 [thread overview]
Message-ID: <20161118081755.GA4425@gmail.com> (raw)
In-Reply-To: <20161118062321.31569-1-lenb@kernel.org>
* Len Brown <lenb@kernel.org> wrote:
> The return from idle path is latency sensitive,
> so the less code and fewer data accesses, the better.
>
> Remove the un-maintained i7300_idle driver,
> the only user of the x86 idle-notifier,
> and then remove the notifier itself.
Acked-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Ingo
prev parent reply other threads:[~2016-11-18 8:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 6:23 [PATCH 0/5] x86: remove idle notifier Len Brown
2016-11-18 6:23 ` [PATCH 1/5] i7300_idle: remove this driver Len Brown
2016-11-18 6:23 ` [PATCH 2/5] x86: remove idle_notifier Len Brown
2016-11-18 11:19 ` [tip:x86/idle] x86/idle: Remove idle_notifier tip-bot for Len Brown
2016-12-06 16:54 ` [PATCH 2/5] x86: remove idle_notifier Pavel Machek
2016-12-07 11:46 ` Thomas Gleixner
2016-12-07 13:40 ` Pavel Machek
2016-12-08 9:18 ` Thomas Gleixner
2016-12-08 22:05 ` Pavel Machek
2016-12-08 22:53 ` Thomas Gleixner
2016-11-18 6:23 ` [PATCH 3/5] x86: remove is_idle flag Len Brown
2016-11-18 11:20 ` [tip:x86/idle] x86/idle: Remove " tip-bot for Len Brown
2016-11-18 6:23 ` [PATCH 4/5] x86: remove x86_test_and_clear_bit_percpu() Len Brown
2016-11-18 11:20 ` [tip:x86/idle] x86: Remove x86_test_and_clear_bit_percpu() tip-bot for Len Brown
2016-11-18 6:23 ` [PATCH 5/5] x86: remove enter_idle(), exit_idle() Len Brown
2016-11-18 11:21 ` [tip:x86/idle] x86/idle: Remove " tip-bot for Len Brown
2016-11-18 11:19 ` [tip:x86/idle] i7300_idle: Remove this driver tip-bot for Len Brown
2016-11-18 8:17 ` Ingo Molnar [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=20161118081755.GA4425@gmail.com \
--to=mingo@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).