From: Michael Ellerman <michael@ellerman.id.au>
To: "wilbur.chan" <wilbur512@gmail.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: How to find macro defination in source code ?
Date: Sat, 19 Jun 2010 15:52:22 +1000 [thread overview]
Message-ID: <1276926742.18166.3.camel@concordia> (raw)
In-Reply-To: <AANLkTikS7AKQ0IaQQebh5MNlXLVEwQmsH8uk5GOwcckd@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
On Sat, 2010-06-19 at 00:47 +0800, wilbur.chan wrote:
> For example, a macro in serial driver 8250.c , SERIAL_PORT_DFNS ,I
> can't find where it is implement.
It looks to be in 8250.c, so I don't know why you can't find it.
> Is there any solutions to find a macro defination in code ?
# make tags
# vi -t SERIAL_PORT_DFNS
Or in general:
http://ctags.sourceforge.net/
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-06-19 5:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 16:47 How to find macro defination in source code ? wilbur.chan
2010-06-18 17:46 ` jjDaNiMoTh
2010-06-19 5:52 ` Michael Ellerman [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=1276926742.18166.3.camel@concordia \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=wilbur512@gmail.com \
/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).