From: navych@126.com (Navy Cheng)
To: kernelnewbies@lists.kernelnewbies.org
Subject: how can I find where is the macro or function deifined
Date: Wed, 29 Jul 2015 01:41:34 +0800 [thread overview]
Message-ID: <20150728174134.GB2384@debian> (raw)
In-Reply-To: <CAAGnT3Zr8TP3qppcnftoXQo5BbgpQKXURu17AMWLu0HAgZ_42A@mail.gmail.com>
On Tue, Jul 28, 2015 at 06:03:16PM +0200, Ahmed Soliman wrote:
> Hi;
> when I used libc I never memorized where each function is located
> beyond the basics (for example I never knew if strlen is in string.h
> or ctype.h or strlib.h )
> I just check out the functions man pages by man strlen
> is their such functionality for the kernel where I dont need to
> memorize the dependencies for example if MODULE_LICENSE is in kernel.h
> or module.h with out using the internel to google them .
>
*make tags* in the root directory of the kernel tree. Then a file named TAGS
is created. TAGS is treated as one part of the tree when *git status*. You
can load it with Vim or emacs. Google it for details.
next prev parent reply other threads:[~2015-07-28 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 16:03 how can I find where is the macro or function deifined Ahmed Soliman
2015-07-28 16:37 ` Manavendra Nath Manav
2015-07-28 17:41 ` Navy Cheng [this message]
2015-07-28 23:54 ` Gnoleba GNOGBO
2015-07-29 0:25 ` Valdis.Kletnieks at vt.edu
2015-07-29 2:54 ` Navy Cheng
2015-07-29 1:14 ` Iuro Nascimento
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=20150728174134.GB2384@debian \
--to=navych@126.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).