From: Chris Mason <clm@fb.com>
To: <paulmck@linux.vnet.ibm.com>
Cc: Omar Sandoval <osandov@osandov.com>, Josef Bacik <jbacik@fb.com>,
<linux-btrfs@vger.kernel.org>,
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>
Subject: Re: [PATCH v2 0/2] Move BTRFS RCU string to common library
Date: Fri, 19 Sep 2014 12:22:57 -0400 [thread overview]
Message-ID: <541C5861.4040403@fb.com> (raw)
In-Reply-To: <20140919160555.GD4723@linux.vnet.ibm.com>
On 09/19/2014 12:05 PM, Paul E. McKenney wrote:
> On Fri, Sep 19, 2014 at 11:47:53AM -0400, Chris Mason wrote:
>>
>>
>> On 09/19/2014 11:45 AM, Paul E. McKenney wrote:
>>> On Fri, Sep 19, 2014 at 02:01:28AM -0700, Omar Sandoval wrote:
>>>> This patch series moves the generic RCU string library used internally by BTRFS
>>>> to be accessible by anyone. It provides printk_in_rcu and
>>>> printk_ratelimited_in_rcu to print these strings. In order to avoid a weird
>>>> inconsistency between the two, the first patch fixes printk_ratelimited so it
>>>> passes on the return value from printk.
>>>>
>>>> The second patch actually moves the RCU string library. Version 2 passes on the
>>>> return values from printk{,_ratelimited} and fixes some style issues.
>>>>
>>>> Omar Sandoval (2):
>>>
>>> For the series:
>>>
>>> Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>>
>> Fine by me too, Paul, do you want to merge it in?
>
> I would be happy to.
>
> Are you thinking in terms of 3.18 or 3.19? These look OK either way, but
> thought I should check.
Either way is fine with me. Actually this will have minor conflicts
with my current branch headed for-next, so I can resolve and send as a
stand alone pull.
-chris
next prev parent reply other threads:[~2014-09-19 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 9:01 [PATCH v2 0/2] Move BTRFS RCU string to common library Omar Sandoval
2014-09-19 9:01 ` [PATCH v2 1/2] Return a value from printk_ratelimited Omar Sandoval
2014-09-19 17:21 ` Steven Rostedt
2014-09-19 18:15 ` Joe Perches
2014-09-21 13:25 ` Paul E. McKenney
2014-09-21 15:53 ` Joe Perches
2014-09-19 9:01 ` [PATCH v2 2/2] Move BTRFS RCU string to common library Omar Sandoval
2014-09-26 23:25 ` josh
2014-09-19 15:45 ` [PATCH v2 0/2] " Paul E. McKenney
2014-09-19 15:47 ` Chris Mason
2014-09-19 16:05 ` Paul E. McKenney
2014-09-19 16:22 ` Chris Mason [this message]
2014-09-21 13:25 ` 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=541C5861.4040403@fb.com \
--to=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;
as well as URLs for NNTP newsgroup(s).