From: Nicholas Mc Guire <der.herr@hofr.at>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Josh Triplett <josh@joshtriplett.org>,
Nicholas Mc Guire <hofrat@osadl.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] rcu: change function declaration to bool
Date: Mon, 11 May 2015 18:21:40 +0200 [thread overview]
Message-ID: <20150511162140.GA10108@opentech.at> (raw)
In-Reply-To: <20150511115935.4d1d27c9@gandalf.local.home>
On Mon, 11 May 2015, Steven Rostedt wrote:
> On Mon, 11 May 2015 17:45:10 +0200
> Nicholas Mc Guire <der.herr@hofr.at> wrote:
>
> - sorry for being so complicated.
>
> Nah, we are the ones being complicated.
>
> > had been putting config info below in all patches - and in git log I do
> > not see that information being included - anyway will move it up and
> > resend in a momemt.
>
> Knowing what config option (or default config build) causes the issues
> is helpful. As for what the patch is against, sometimes its best to say
> what commit the patch fixes. That even has a tag for it.
>
gave it one more shot - let me know if that fits - about time I get these
basics right...
thx!
hofrat
next prev parent reply other threads:[~2015-05-11 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 15:10 [PATCH V2] rcu: change function declaration to bool Nicholas Mc Guire
2015-05-11 15:28 ` Steven Rostedt
2015-05-11 15:37 ` Josh Triplett
2015-05-11 15:45 ` Nicholas Mc Guire
2015-05-11 15:59 ` Steven Rostedt
2015-05-11 16:21 ` Nicholas Mc Guire [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-11 15:46 Nicholas Mc Guire
2015-05-11 16:11 ` Josh Triplett
2015-05-11 16:58 ` Paul E. McKenney
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=20150511162140.GA10108@opentech.at \
--to=der.herr@hofr.at \
--cc=hofrat@osadl.org \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.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.