From: Len Brown <lenb@kernel.org>
To: linux-pm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/13] intel_idle patches ready for upstream
Date: Wed, 6 Apr 2016 17:00:46 -0400 [thread overview]
Message-ID: <1459976459-2532-1-git-send-email-lenb@kernel.org> (raw)
Bug fixes, plus add a few more table entires for new model #'s.
Some of the BXT table entries will be replaced by values read
from processor configuration registers at boot-time.
Let me know if you see troubles with any of these patches.
They are all available on this git branch:
git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux.git cpuidle
thanks,
-Len Brown, Intel Open Source Technology Center
next reply other threads:[~2016-04-06 21:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 21:00 Len Brown [this message]
2016-04-06 21:00 ` [PATCH 01/13] intel_idle: add BXT support Len Brown
2016-04-06 21:00 ` [PATCH 02/13] intel_idle: remove useless return from void function Len Brown
2016-04-06 21:00 ` [PATCH 03/13] intel_idle: Fix a helper function's return value Len Brown
2016-04-06 21:00 ` [PATCH 04/13] intel_idle: Remove redundant initialization calls Len Brown
2016-04-06 21:00 ` [PATCH 05/13] intel_idle: Fix deallocation order on the driver exit path Len Brown
2016-04-06 21:00 ` [PATCH 06/13] intel_idle: Fix dangling registration on error path Len Brown
2016-04-06 21:00 ` [PATCH 07/13] intel_idle: Avoid a double free of the per-CPU data Len Brown
2016-04-06 21:00 ` [PATCH 08/13] intel_idle: Setup the timer broadcast only on successful driver load Len Brown
2016-04-06 21:00 ` [PATCH 09/13] intel_idle: Don't overreact to a cpuidle registration failure Len Brown
2016-04-06 21:00 ` [PATCH 10/13] intel_idle: Propagate hot plug errors Len Brown
2016-04-06 21:00 ` [PATCH 11/13] intel_idle: Clean up all registered devices on exit Len Brown
2016-04-06 21:00 ` [PATCH 12/13] intel_idle: Add SKX support Len Brown
2016-04-06 21:00 ` [PATCH 13/13] intel_idle: Add KBL support Len Brown
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=1459976459-2532-1-git-send-email-lenb@kernel.org \
--to=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.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 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.