public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: jolsa@redhat.com
To: mingo@elte.hu, rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: [PATCH 3/3] tracing: removing .globl in the scripts/recordmcount.pl doc
Date: Thu, 16 Jul 2009 19:44:28 +0000	[thread overview]
Message-ID: <1247773468-11594-4-git-send-email-jolsa@redhat.com> (raw)
In-Reply-To: <1247773468-11594-1-git-send-email-jolsa@redhat.com>

I was reading throught the recordmcount.pl starting comment,
and spot a tiny discrepancy.

The second example is about my_func not being global, but the example code
has the ".globl my_func" statement just moved. IMO it should be erased,
if not I'm curious what I'm missing.. :)

wbr,
jirka

Signed-off-by: Jiri Olsa <jolsa@redhat.com>

---
 scripts/recordmcount.pl |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/scripts/recordmcount.pl b/scripts/recordmcount.pl
index 7109e2b..db4ebe1 100755
--- a/scripts/recordmcount.pl
+++ b/scripts/recordmcount.pl
@@ -57,7 +57,6 @@
 #        call mcount  (offset: 0x5)
 #        [...]
 #        ret
-#  .globl my_func
 #  other_func:
 #        [...]
 #        call mcount (offset: 0x1b)
-- 
1.6.2.5


      parent reply	other threads:[~2009-07-16 19:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16 19:44 [PATCH 0/3] tracing: minor bugs jolsa
2009-07-16 19:44 ` [PATCH 1/3] tracing: removing not used variables jolsa
2009-07-16 19:44 ` [PATCH 2/3] tracing: removing struct module* parameter from ftrace_init_module code path jolsa
2009-07-18 10:16   ` [PATCH 2/3] tracing: removing struct module* parameter from Ingo Molnar
2009-07-19 18:47     ` Jiri Olsa
2009-07-16 19:44 ` jolsa [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=1247773468-11594-4-git-send-email-jolsa@redhat.com \
    --to=jolsa@redhat.com \
    --cc=kernel-janitors@vger.kernel.org \
    --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