From: mantykuma@gmail.com (manty kuma)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to browse the code
Date: Wed, 12 Apr 2017 08:56:16 +0900 [thread overview]
Message-ID: <CAB6A5-CR29+VqS5Db7GheVHkMR=a-c+WR-xO4S-x9hYqqNDZPw@mail.gmail.com> (raw)
In-Reply-To: <CAC+QLdTQOmurxnb=TXCC27b9qaYOVTBYYs1QvauHR4TcbAr4VA@mail.gmail.com>
I like Opengrok. It is insanely fast in giving search results. However it
takes sometime to setup and you need to index it before the first use.
If you are ok with browsing someold kernels, then you can use this link
http://androidxref.com/kernel_3.18/ which is maintained privately.
If you want to use opengrok on more recent linux releases, you may have to
set it up yourself.
On Wed, Apr 12, 2017 at 5:13 AM, Mandeep Sandhu <mandeepsandhu.chd@gmail.com
> wrote:
>
>> I am looking for something that can list all the places that a certain
>> field of a certain structure is used. For example, sk_buff has a field
>> called destructor, but so do many other data structures. How do I
>> search for places where just the destructor field of sk_buff.
>>
>
> I think lxr has an identifier & free-text search (powered by google). If
> that doesn't do it for you, you can go "old school" and try cscope maybe?
>
> HTH,
> -mandeep
>
>
>
>>
>> Thanks a lot.
>>
>> --
>> CS1
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170412/b3fc54eb/attachment.html
next prev parent reply other threads:[~2017-04-11 23:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 19:17 How to browse the code Code Soldier1
2017-04-11 20:13 ` Mandeep Sandhu
2017-04-11 23:56 ` manty kuma [this message]
[not found] ` <CABGNecz-3SU=yfPQEJKM_uLd3-7Opn01S30ymOidpGF3cJY23Q@mail.gmail.com>
2017-04-13 10:39 ` manty kuma
2017-04-13 11:41 ` Daniel.
2017-04-13 11:50 ` Quentin Lambert
2017-04-13 14:22 ` valdis.kletnieks at vt.edu
[not found] ` <CABGNeczyadNCKYjLwWoK8N3o9dJdseUrAYCwFPx16DFr2Je7ng@mail.gmail.com>
2017-04-12 21:28 ` Mandeep Sandhu
[not found] ` <CABGNecxf3RnZH-kJ2VbC5JPuj=0Ka-1GPBA2x5R_tYyHLLm5EQ@mail.gmail.com>
[not found] ` <CAC+QLdTbDM9kTxE96ErcrHNMCoEhNbV1LKU+xcWaxj+j_DP1aA@mail.gmail.com>
2017-04-12 21:47 ` Mandeep Sandhu
2017-04-13 2:23 ` Aruna Hewapathirane
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='CAB6A5-CR29+VqS5Db7GheVHkMR=a-c+WR-xO4S-x9hYqqNDZPw@mail.gmail.com' \
--to=mantykuma@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.