From: Stefani Seibold <stefani@seibold.net>
To: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH] ctags usability fix
Date: Sat, 01 Aug 2009 10:13:13 +0200 [thread overview]
Message-ID: <1249114393.19594.16.camel@wall-e> (raw)
Hi,
the tag file generated by the tags.sh script has some issue.
First:
The identifier-list miss the
DEFINE_TRACE,EXPORT_TRACEPOINT_SYMBOL,EXPORT_TRACEPOINT_SYMBOL_GPL
special handling, which can result in a wrong tag, not to jump to the
right variable definition or function implementation.
Second:
It makes no real sense to include function prototypes and external and
forward variable declarations, because jumping to a tag will sometimes
go to this and not to the real definition and implementation. The information
about the declaration is still there at the definition and implementation
place.
So this patch make it lot easier to navigate through the kernel source
tree using vi.
Greetings,
Stefani
tags.sh | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Signed-off-by: Stefani Seibold <stefani@seibold.net>
--- linux-2.6.30.orig/scripts/tags.sh 2009-06-10 05:05:27.000000000 +0200
+++ linux-2.6.30/scripts/tags.sh 2009-08-01 09:46:56.000000000 +0200
@@ -101,7 +101,8 @@
-I ____cacheline_aligned_in_smp \
-I ____cacheline_internodealigned_in_smp \
-I EXPORT_SYMBOL,EXPORT_SYMBOL_GPL \
- --extra=+f --c-kinds=+px \
+ -I DEFINE_TRACE,EXPORT_TRACEPOINT_SYMBOL,EXPORT_TRACEPOINT_SYMBOL_GPL \
+ --extra=+f --c-kinds=-px \
--regex-asm='/^ENTRY\(([^)]*)\).*/\1/' \
--regex-c='/^SYSCALL_DEFINE[[:digit:]]?\(([^,)]*).*/sys_\1/'
next reply other threads:[~2009-08-01 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 8:13 Stefani Seibold [this message]
2009-08-03 8:58 ` [PATCH] ctags usability fix Amerigo Wang
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=1249114393.19594.16.camel@wall-e \
--to=stefani@seibold.net \
--cc=akpm@linux-foundation.org \
--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