All of lore.kernel.org
 help / color / mirror / Atom feed
From: jsitnicki@gmail.com (Jakub Sitnicki)
To: kernelnewbies@lists.kernelnewbies.org
Subject: unable to find function definition
Date: Wed, 27 Apr 2016 22:26:26 +0200	[thread overview]
Message-ID: <87oa8u4x3h.fsf@frog.home> (raw)
In-Reply-To: <2cab8174b247724af07b444437ee423c@sillymon.ch>

On Tue, Apr 26, 2016 at 12:45 PM CEST, Silvan Jegen <me@sillymon.ch> wrote:
> Am 2016-04-26 10:50, schrieb Gadre Nayan:
>> Ctags can help. Ctags -R on the entire source.
>
> In the Kernel Makefile there is actually a target for this. It's called 
> either 'tags' or 'tag' so
>
> make tags [or tag]
>
> should create the ctag file for you.

An alternative would be to use cscope:

$ # build the index (will take a moment)
$ make cscope
$ # find all assignments to a symbol
$ cscope -d -L -9 platform_gpio_blink_set
drivers/leds/leds-gpio.c <global> 130 led_dat->platform_gpio_blink_set = blink_set;
$ # or find all occurrences of a symbol and grep for assignments
$ cscope -d -L -0 platform_gpio_blink_set | grep =
drivers/leds/leds-gpio.c <global> 130 led_dat->platform_gpio_blink_set = blink_set;

The latter, for some reason, runs faster for me.

-Jakub

  parent reply	other threads:[~2016-04-27 20:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20  6:17 unable to find function definition Nijam Haider
2016-04-20  7:26 ` Cihangir Akturk
2016-04-26  8:30   ` Jay Aurabind
2016-04-26  8:50     ` Gadre Nayan
2016-04-26 10:45       ` Silvan Jegen
2016-04-26 12:56         ` Jay Aurabind
2016-04-26 13:31           ` Silvan Jegen
2016-04-26 15:24             ` Valdis.Kletnieks at vt.edu
2016-04-26 15:33               ` Silvan Jegen
2016-04-27 20:26         ` Jakub Sitnicki [this message]
2016-04-28  4:23           ` Anupam Kapoor
2016-04-27  1:35     ` John de la Garza
2016-04-27  3:05       ` Jay Aurabind
2016-04-27  3:10         ` nizam haider

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=87oa8u4x3h.fsf@frog.home \
    --to=jsitnicki@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.