From: Luis Henriques <henrix@sapo.pt>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH -tip] tracing: remove unused code
Date: Fri, 27 Feb 2009 20:29:24 +0000 [thread overview]
Message-ID: <20090227202923.GA3826@hades.domain.com> (raw)
struct file_operations tracing_lt_fops and tracing_lt_open are not used
anywhere. These are legacy from the /debug/tracing/latency_trace, which has
been removed in commit 886b5b73d71e4027d7dc6c14f5f7ab102201ea6b
Signed-off-by: Luis Henriques <henrix@sapo.pt>
---
kernel/trace/trace.c | 22 ----------------------
1 files changed, 0 insertions(+), 22 deletions(-)
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 5db7485..04306a1 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -1822,21 +1822,6 @@ static int tracing_open(struct inode *inode, struct file *file)
return ret;
}
-static int tracing_lt_open(struct inode *inode, struct file *file)
-{
- struct trace_iterator *iter;
- int ret = 0;
-
- iter = __tracing_open(inode, file);
-
- if (IS_ERR(iter))
- ret = PTR_ERR(iter);
- else
- iter->iter_flags |= TRACE_FILE_LAT_FMT;
-
- return ret;
-}
-
static void *
t_next(struct seq_file *m, void *v, loff_t *pos)
@@ -1916,13 +1901,6 @@ static struct file_operations tracing_fops = {
.release = tracing_release,
};
-static struct file_operations tracing_lt_fops = {
- .open = tracing_lt_open,
- .read = seq_read,
- .llseek = seq_lseek,
- .release = tracing_release,
-};
-
static struct file_operations show_traces_fops = {
.open = show_traces_open,
.read = seq_read,
--
1.6.1.3
next reply other threads:[~2009-02-27 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 20:29 Luis Henriques [this message]
2009-02-27 20:36 ` [PATCH -tip] tracing: remove unused code Steven Rostedt
2009-02-28 7:21 ` Ingo Molnar
2009-02-28 19:40 ` Luis Henriques
2009-02-28 19:54 ` Frederic Weisbecker
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=20090227202923.GA3826@hades.domain.com \
--to=henrix@sapo.pt \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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