From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-pm@vger.kernel.org,
Arjan van de Ven <arjan@linux.intel.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFC 0/1] Delete legacy power trace API
Date: Sat, 05 Jan 2013 23:10:46 +0100 [thread overview]
Message-ID: <5190666.Mu6UtpjCCL@vostro.rjw.lan> (raw)
In-Reply-To: <1357350544-32704-1-git-send-email-paul.gortmaker@windriver.com>
On Friday, January 04, 2013 08:49:03 PM Paul Gortmaker wrote:
> 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.
Do you want me or the tracing maintainers to handle this?
Rafael
> ---
>
> 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(-)
>
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-01-05 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 1:49 [PATCH/RFC 0/1] Delete legacy power trace API Paul Gortmaker
2013-01-05 1:49 ` [PATCH 1/1] tracing: remove deprecated " Paul Gortmaker
2013-01-05 22:10 ` Rafael J. Wysocki [this message]
2013-01-06 0:17 ` [PATCH/RFC 0/1] Delete legacy " 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=5190666.Mu6UtpjCCL@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=arjan@linux.intel.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--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 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.