mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Munsie <imunsie@au1.ibm.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Fwd: [PATCH] tags, powerpc: Update tags.sh to support _GLOBAL symbols
Date: Fri, 19 Aug 2011 09:32:57 +1000	[thread overview]
Message-ID: <1313710351-sup-4548@au1.ibm.com> (raw)

I seem to have missed LKML in the CC for this patch...

--- Begin forwarded message from Ian Munsie ---
From: Ian Munsie <imunsie@au1.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>, Michal Marek <mmarek@suse.cz>
Cc: Ian Munsie <imunsie@au1.ibm.com>, linux-kbuild <linux-kbuild@vger.kernel.org>
Date: Wed, 17 Aug 2011 16:25:47 +1000
Subject: [PATCH] tags, powerpc: Update tags.sh to support _GLOBAL symbols

From: Ian Munsie <imunsie@au1.ibm.com>

On PowerPC we use _GLOBAL throughout the assembly to define symbols, but
currently these symbols are missing from the tags generated with
ARCH=powerpc make tags. This patch modifies the tags.sh script to
recognise _GLOBAL(.*) so that these symbols will be in the tags.

This is almost (but not quite) PowerPC specific and this change should
not affect anyone else:

$ git grep -E '^_GLOBAL\(([^)]*)\).*' |sed 's/^\([^/]*\/[^/]*\)\/.*$/\1/'|uniq -c
    627 arch/powerpc
      2 arch/um

Signed-off-by: Ian Munsie <imunsie@au1.ibm.com>
---
 scripts/tags.sh |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/tags.sh b/scripts/tags.sh
index 75c5d24f1..38f6617 100755
--- a/scripts/tags.sh
+++ b/scripts/tags.sh
@@ -129,7 +129,7 @@ exuberant()
     -I EXPORT_SYMBOL,EXPORT_SYMBOL_GPL                      \
     -I DEFINE_TRACE,EXPORT_TRACEPOINT_SYMBOL,EXPORT_TRACEPOINT_SYMBOL_GPL \
     --extra=+f --c-kinds=+px                                \
-    --regex-asm='/^ENTRY\(([^)]*)\).*/\1/'                  \
+    --regex-asm='/^(ENTRY|_GLOBAL)\(([^)]*)\).*/\2/'        \
     --regex-c='/^SYSCALL_DEFINE[[:digit:]]?\(([^,)]*).*/sys_\1/' \
     --regex-c++='/^TRACE_EVENT\(([^,)]*).*/trace_\1/'        \
     --regex-c++='/^DEFINE_EVENT\([^,)]*, *([^,)]*).*/trace_\1/'
@@ -151,7 +151,7 @@ exuberant()
 emacs()
 {
     all_sources | xargs $1 -a                               \
-    --regex='/^ENTRY(\([^)]*\)).*/\1/'                      \
+    --regex='/^(ENTRY|_GLOBAL)(\([^)]*\)).*/\2/'            \
     --regex='/^SYSCALL_DEFINE[0-9]?(\([^,)]*\).*/sys_\1/'   \
     --regex='/^TRACE_EVENT(\([^,)]*\).*/trace_\1/'        \
     --regex='/^DEFINE_EVENT([^,)]*, *\([^,)]*\).*/trace_\1/'
--- End forwarded message ---

                 reply	other threads:[~2011-08-18 23:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1313710351-sup-4548@au1.ibm.com \
    --to=imunsie@au1.ibm.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®