From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: linux-pm@vger.kernel.org
Cc: Arjan van de Ven <arjan@linux.intel.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: [PATCH/RFC 0/1] Delete legacy power trace API
Date: Fri, 4 Jan 2013 20:49:03 -0500 [thread overview]
Message-ID: <1357350544-32704-1-git-send-email-paul.gortmaker@windriver.com> (raw)
The actual deletion is mind-numbingly simple; and if you go by the
comments in the code, it is well overdue. However, in discussions
with Frederic, he suggested to me that those comments might have
been overly optimistic, and that there may still be people out
there who are still unknowingly using this dead API.
So, that is the crux of the RFC component -- to check whether the
comments saying "delete by v3.1" can be taken at face value, or
whether they were overly optimistic, and hence this stuff is still
actively used even though it is overdue for deletion.
Thanks,
Paul.
---
Paul Gortmaker (1):
tracing: remove deprecated power trace API
Documentation/trace/events-power.txt | 27 +----------
arch/arm/mach-omap2/pm34xx.c | 2 -
arch/x86/kernel/process.c | 6 ---
drivers/cpufreq/cpufreq.c | 1 -
drivers/cpuidle/cpuidle.c | 2 -
include/trace/events/power.h | 92 ------------------------------------
kernel/trace/Kconfig | 15 ------
kernel/trace/power-traces.c | 3 --
8 files changed, 1 insertion(+), 147 deletions(-)
--
1.8.1
next reply other threads:[~2013-01-05 1:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 1:49 Paul Gortmaker [this message]
2013-01-05 1:49 ` [PATCH 1/1] tracing: remove deprecated power trace API Paul Gortmaker
2013-01-05 22:10 ` [PATCH/RFC 0/1] Delete legacy " Rafael J. Wysocki
2013-01-06 0:17 ` Paul Gortmaker
2013-01-06 22:13 ` Steven Rostedt
2013-01-06 22:28 ` Rafael J. Wysocki
2013-01-11 22:32 ` Rafael J. Wysocki
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=1357350544-32704-1-git-send-email-paul.gortmaker@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=arjan@linux.intel.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rostedt@goodmis.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).