From: Andrew Morton <akpm@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: paulmck@linux.vnet.ibm.com, LKML <linux-kernel@vger.kernel.org>,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [PATCH] rcu: Make struct rcu_head searchable
Date: Wed, 13 Nov 2013 10:57:05 -0800 [thread overview]
Message-ID: <20131113105705.c3fed1c5.akpm@linux-foundation.org> (raw)
In-Reply-To: <20131113131044.677cdc74@gandalf.local.home>
On Wed, 13 Nov 2013 13:10:44 -0500 Steven Rostedt <rostedt@goodmis.org> wrote:
> On Wed, 13 Nov 2013 09:12:05 -0800
> "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
>
> > On Wed, Nov 13, 2013 at 12:02:25PM -0500, Steven Rostedt wrote:
> > > After wasting too much time trying to see where struct rcu_head was
> > > declared, I finally found it in include/linux/types.h as a define for
> > > callback_head!
> > >
> > > To prevent other developers from wasting their precious time in
> > > searching for this structure, add a comment to help them find it!
> > >
> > > Cc: Al Viro <viro@ZenIV.linux.org.uk>
> > > Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> > > Signed-off-by: Steven "frustrated" Rostedt <rostedt@goodmis.org>
> >
> > The cscope tool is your friend in this case, but nevertheless:
>
> I use emacs, and the latest version of etags (or emacs) brings you to
> each use case before it gets you to the define (which is really
> annoying). Back in 2006 it use to work properly. I need to figure out
> what changed :-/
That irritates me too. Fortunately I just invented
(grep "#define" tags && grep -v "#define" tags) > tags.new
next prev parent reply other threads:[~2013-11-13 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 17:02 Steven Rostedt
2013-11-13 17:12 ` Paul E. McKenney
2013-11-13 18:10 ` Steven Rostedt
2013-11-13 18:57 ` Andrew Morton [this message]
2013-11-13 19:05 ` Steven Rostedt
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=20131113105705.c3fed1c5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=viro@ZenIV.linux.org.uk \
/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®