linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Omar Sandoval <osandov@osandov.com>
Cc: Chris Mason <clm@fb.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 08:45:46 -0700	[thread overview]
Message-ID: <20140919154546.GZ4723@linux.vnet.ibm.com> (raw)
In-Reply-To: <cover.1411116672.git.osandov@osandov.com>

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>

>   Return a value from printk_ratelimited
>   Move BTRFS RCU string to common library
> 
>  fs/btrfs/check-integrity.c |  6 +--
>  fs/btrfs/dev-replace.c     | 19 +++++-----
>  fs/btrfs/disk-io.c         |  6 +--
>  fs/btrfs/extent_io.c       |  4 +-
>  fs/btrfs/ioctl.c           |  4 +-
>  fs/btrfs/raid56.c          |  2 +-
>  fs/btrfs/rcu-string.h      | 56 ----------------------------
>  fs/btrfs/scrub.c           | 15 ++++----
>  fs/btrfs/super.c           |  2 +-
>  fs/btrfs/volumes.c         | 14 +++----
>  include/linux/printk.h     |  4 +-
>  include/linux/rcustring.h  | 91 ++++++++++++++++++++++++++++++++++++++++++++++
>  12 files changed, 131 insertions(+), 92 deletions(-)
>  delete mode 100644 fs/btrfs/rcu-string.h
>  create mode 100644 include/linux/rcustring.h
> 
> -- 
> 2.1.0
> 


  parent reply	other threads:[~2014-09-19 15:45 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 ` Paul E. McKenney [this message]
2014-09-19 15:47   ` [PATCH v2 0/2] " Chris Mason
2014-09-19 16:05     ` Paul E. McKenney
2014-09-19 16:22       ` Chris Mason
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=20140919154546.GZ4723@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.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=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).