From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com, agk@redhat.com
Subject: Re: Fw: [PATCH tip/core/rcu 4/9] dm: sparse: Annotate field with __rcu for checking
Date: Tue, 28 Oct 2014 19:43:19 -0700 [thread overview]
Message-ID: <20141029024319.GI5718@linux.vnet.ibm.com> (raw)
In-Reply-To: <20141029002513.GE29288@redhat.com>
On Tue, Oct 28, 2014 at 08:25:13PM -0400, Mike Snitzer wrote:
> On Tue, Oct 28 2014 at 7:49pm -0400,
> Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
>
> > And similarly for this one on both counts.
>
> Yeap, I'll take it, thanks.
Very good, I will drop both from my tree.
Thanx, Paul
prev parent reply other threads:[~2014-10-29 2:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 23:49 Fw: [PATCH tip/core/rcu 4/9] dm: sparse: Annotate field with __rcu for checking Paul E. McKenney
2014-10-29 0:25 ` Mike Snitzer
2014-10-29 2:43 ` Paul E. McKenney [this message]
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=20141029024319.GI5718@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=snitzer@redhat.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 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.