From: Sam Ravnborg <sam@ravnborg.org>
To: Masatake YAMATO <jet@gyve.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Adding symbols in Kconfig and defconfig to TAGS
Date: Sat, 24 Jun 2006 23:52:49 +0200 [thread overview]
Message-ID: <20060624215249.GB8904@mars.ravnborg.org> (raw)
In-Reply-To: <20060622.122120.261356707.yamato@redhat.com>
On Thu, Jun 22, 2006 at 12:21:20PM +0900, Masatake YAMATO wrote:
> I'm using TAGS generated from "make TAGS" to read the kernel source code.
>
> When I met a ifdef block
>
> #ifdef CONFIG_FOO
> ...
> #endif
>
> in the soruce code I would like to know the meaning CONFIG_FOO
> to decide whether I should read inside the ifdef block
> or not. meaning CONFIG_FOO is well documented in Kconfig.
> So it is nice if I can jump to CONFIG_FOO entry in Kconfig
> from "#ifdef CONFIG_FOO" with the tag jump.
>
> Here is the patch to add symbols in Kconfig and defconfig to TAGS
> in "make TAGS" operation.
Applied after fixing 80 coloumn breakage.
Sam
prev parent reply other threads:[~2006-06-24 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 3:21 Masatake YAMATO
2006-06-24 21:52 ` Sam Ravnborg [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=20060624215249.GB8904@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jet@gyve.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
all inboxes | Powered by JetHome®