From: Zhang Le <robert@thizgroup.com>
To: Aneesh Kumar <aneesh.kumar@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Add entry.S function name to tag file
Date: Thu, 19 Jan 2006 11:52:57 +0800 [thread overview]
Message-ID: <43CF0D19.6050009@thizgroup.com> (raw)
In-Reply-To: <cc723f590601172058n67fb2200ybfffba9bc4fc72ba@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Aneesh Kumar wrote:
> How about a patch like the one attached below. I am not sure whether i
> got the regular expression correct. But it works for me.
>
> -aneesh
>
> ----------------------------------------------------------------------
>
> diff --git a/Makefile b/Makefile
> index 252a659..6c8479e 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1272,7 +1272,7 @@ define cmd_tags
> CTAGSF=`ctags --version | grep -i exuberant >/dev/null && \
> echo "-I __initdata,__exitdata,__acquires,__releases \
> -I EXPORT_SYMBOL,EXPORT_SYMBOL_GPL \
> - --extra=+f --c-kinds=+px"`; \
> + --extra=+f --c-kinds=+px
--regex-asm=/ENTRY\(([^)]*)\).*/\1/f/"`; \
> $(all-sources) | xargs ctags $$CTAGSF -a
> endef
>
In fact, ENTRY()'s are not functions
they are just label's
some are functions
some are variables
no need to add "f" here
the following is just OK
- --regex-asm=/ENTRY\(([^)]*)\).*/\1/"
the only difference between tags file generated from these two
different option
is like this
- -alignment_check arch/i386/kernel/entry.S
/^ENTRY(alignment_check)$/;" r
+alignment_check arch/i386/kernel/entry.S
/^ENTRY(alignment_check)$/;" f
- --
Zhang Le, Robert
Linux Engineer/Trainer
Institute of Thiz Technology Limited
Address: Unit 1004, 10/F, Tower B,
Hunghom Commercial Centre, 37 Ma Tau Wai Road,
To Kwa Wan, Kowloon, Hong Kong
Telephone: (852) 2735 2725
Mobile:(852) 9845 4336
Fax: (852) 2111 0702
URL: http://www.thizgroup.com
Public key: gpg --keyserver pgp.mit.edu --recv-keys 1E4E2973
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFDzw0ZvFHICB5OKXMRAsyGAJ0TeXETc5OxTaovom9YHxzQkcbpyACeLJ58
Ztl/ug1VR4JoNM8nzIwTwyk=
=zQwU
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-01-19 3:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 4:58 Add entry.S function name to tag file Aneesh Kumar
2006-01-19 2:40 ` Zhang Le
2006-01-19 3:52 ` Zhang Le [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=43CF0D19.6050009@thizgroup.com \
--to=robert@thizgroup.com \
--cc=aneesh.kumar@gmail.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