All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Steven Rostedt <srostedt@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ftrace: eh?
Date: Thu, 24 Jul 2008 08:11:29 +0200	[thread overview]
Message-ID: <20080724061129.GA15772@elte.hu> (raw)
In-Reply-To: <4887B07D.4080000@goop.org>


* Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> kernel/trace/trace.c:s_next():
>
> 	if (last_ent && !ent)
> 		seq_puts(m, "\n\nvim:ft=help\n");
>
> eh?

uhm, yes, that was me, years ago when i wrote the original version of 
the latency tracer. If you look at such traces via vim then portions of 
the trace will be color highlighted automatically with that tag in 
place.

Thanks for the reminder, i've removed it via the patch below.

	Ingo

------------>
commit 1986b0cb1671ea39178b4e2b00461109728fc935
Author: Ingo Molnar <mingo@elte.hu>
Date:   Thu Jul 24 08:10:02 2008 +0200

    ftrace: remove latency-tracer leftover
    
    remove the :vim=ft=help tag from trace files.
    
    I used them years ago to syntax-highlight traces and forgot about this hack.
    
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 kernel/trace/trace.c |    3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)

diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 868e121..fc20e09 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -1203,9 +1203,6 @@ static void *s_next(struct seq_file *m, void *v, loff_t *pos)
 
 	iter->pos = *pos;
 
-	if (last_ent && !ent)
-		seq_puts(m, "\n\nvim:ft=help\n");
-
 	return ent;
 }
 

      reply	other threads:[~2008-07-24  6:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23 22:28 ftrace: eh? Jeremy Fitzhardinge
2008-07-24  6:11 ` 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=20080724061129.GA15772@elte.hu \
    --to=mingo@elte.hu \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srostedt@redhat.com \
    /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.