mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesper Juhl <juhl-lkml@dif.dk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: David Addison <addy@quadrics.com>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Andrea Arcangeli <andrea@suse.de>,
	David Addison <david.addison@quadrics.com>
Subject: Re: [PATCH][RFC] Linux VM hooks for advanced RDMA NICs
Date: Tue, 26 Apr 2005 19:38:26 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.62.0504261934220.2071@dragon.hyggekrogen.localhost> (raw)
In-Reply-To: <1114536511.5410.14.camel@mindpipe>

On Tue, 26 Apr 2005, Lee Revell wrote:

> On Tue, 2005-04-26 at 19:20 +0200, Jesper Juhl wrote:
> > I don't know what you do, but when I'm grep'ing the tree for some function 
> > I'm often looking for its return type, having that on the same line as the 
> > function name lets me grep for the function name and the grep output will 
> > contain the return type and function name nicely on the same line.
> > 
> 
> I do a lot of looking at large hunks of code I'm not familiar with and
> trying to figure out how it works.  It's quite handy to grep for
> foo_func to see all usages, then ^foo_func to see the function.

Have you ever looked at what "make tags" gives you?
Run  make tags  in the kernel source dir, then open up a source file in 
vim, place the cursor over some struct name or function name and press 
CTRL+] and you'll be taken to the definition, you can drill down several 
levels like that, and if you want to go back up one level to where you 
were you simply press CTRL+t  very useful when navigating the source.

-- 
Jesper



  reply	other threads:[~2005-04-26 17:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-26 15:49 David Addison
2005-04-26 16:57 ` Jesper Juhl
2005-04-26 17:13   ` Lee Revell
2005-04-26 17:20     ` Jesper Juhl
2005-04-26 17:28       ` Lee Revell
2005-04-26 17:38         ` Jesper Juhl [this message]
2005-04-26 20:14         ` John W. Linville
2005-04-26 20:17           ` Lee Revell
2005-04-26 20:09       ` Lars Marowsky-Bree
2005-04-28 11:34     ` Jakob Oestergaard
2005-04-29  8:22     ` Benjamin Herrenschmidt
2005-04-26 17:06 ` Brice Goglin
2005-04-27  9:41   ` David Addison
2005-04-28  8:38     ` Andy Isaacson
2005-04-27 13:43   ` Andi Kleen
2005-04-28  1:42 ` Troy Benjegerdes
2005-04-28  7:21 ` Brice Goglin
2005-04-28  9:21   ` David Addison
2005-04-29  8:19   ` Benjamin Herrenschmidt
2005-04-29  9:25     ` David Addison

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=Pine.LNX.4.62.0504261934220.2071@dragon.hyggekrogen.localhost \
    --to=juhl-lkml@dif.dk \
    --cc=addy@quadrics.com \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=david.addison@quadrics.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.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

all inboxes | Powered by JetHome®