From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] rcu: Make struct rcu_head searchable
Date: Wed, 13 Nov 2013 09:12:05 -0800 [thread overview]
Message-ID: <20131113171205.GG4138@linux.vnet.ibm.com> (raw)
In-Reply-To: <20131113120225.3aacae13@gandalf.local.home>
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:
Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> diff --git a/include/linux/types.h b/include/linux/types.h
> index 4d118ba..073e9a8 100644
> --- a/include/linux/types.h
> +++ b/include/linux/types.h
> @@ -210,6 +210,9 @@ struct callback_head {
> struct callback_head *next;
> void (*func)(struct callback_head *head);
> };
> +/*
> + * Make "struct rcu_head {" seachable with this comment.
> + */
> #define rcu_head callback_head
>
> #endif /* __ASSEMBLY__ */
>
next prev parent reply other threads:[~2013-11-13 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 17:02 [PATCH] rcu: Make struct rcu_head searchable Steven Rostedt
2013-11-13 17:12 ` Paul E. McKenney [this message]
2013-11-13 18:10 ` Steven Rostedt
2013-11-13 18:57 ` Andrew Morton
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=20131113171205.GG4138@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.