diff options
| author | Masatake YAMATO <jet@gyve.org> | 2006-06-22 12:21:20 +0900 |
|---|---|---|
| committer | Sam Ravnborg <sam@mars.ravnborg.org> | 2006-06-24 23:52:05 +0200 |
| commit | e838db685fcfd2e9a0548ffc5cb9447e6c3c11be (patch) | |
| tree | 980366e83c7bf2c9ece3f0ad77eb62dc8ee8fbc5 /drivers/leds/led-triggers.c | |
| parent | 6803dc0ea85ad21b2cb3ec88decff5e27d7a390b (diff) | |
kbuild: adding symbols in Kconfig and defconfig to TAGS
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.
Signed-off-by: Masatake YAMATO <jet@gyve.org>
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Diffstat (limited to 'drivers/leds/led-triggers.c')
0 files changed, 0 insertions, 0 deletions