From: Joe Perches <joe@perches.com>
To: Chris Mason <clm@fb.com>
Cc: Omar Sandoval <osandov@osandov.com>, Josef Bacik <jbacik@fb.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v5] Move BTRFS RCU string to common library
Date: Fri, 07 Nov 2014 16:39:15 -0800 [thread overview]
Message-ID: <1415407155.23530.24.camel@perches.com> (raw)
In-Reply-To: <1415391689.9491.0@mail.thefacebook.com>
On Fri, 2014-11-07 at 15:21 -0500, Chris Mason wrote:
>
> On Fri, Nov 7, 2014 at 3:17 PM, Omar Sandoval <osandov@osandov.com>
> wrote:
> > The RCU-friendly string API used internally by BTRFS is generic
> > enough for
> > common use. This doesn't add any new functionality, but instead just
> > moves the
> > code and documents the existing API.
> >
> > Reviewed-by: Josh Triplett <josh@joshtriplett.org>
> > Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > Signed-off-by: Omar Sandoval <osandov@osandov.com>
> > ---
> > Chris, could you take a look at this again? It's just been rebased
> > and should
> > be good to go. Thanks!
>
> Thanks Omar, I'm pulling this into a branch for the next merge window.
> Looks good to me.
rcustring.h should probably #include any #include dependencies
it has. types.h, printk.h, etc...
next prev parent reply other threads:[~2014-11-08 0:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 20:17 [PATCH v5] Move BTRFS RCU string to common library Omar Sandoval
2014-11-07 20:21 ` Chris Mason
2014-11-08 0:39 ` Joe Perches [this message]
2014-11-08 8:46 ` [PATCH v6] " Omar Sandoval
2014-11-08 16:13 ` Joe Perches
2014-11-09 7:32 ` Omar Sandoval
2014-11-13 10:18 ` [PATCH v7] " Omar Sandoval
2014-11-20 22:10 ` Omar Sandoval
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=1415407155.23530.24.camel@perches.com \
--to=joe@perches.com \
--cc=clm@fb.com \
--cc=jbacik@fb.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=osandov@osandov.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox