[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140919154546.GZ4723@linux.vnet.ibm.com>
Date: Fri, 19 Sep 2014 08:45:46 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Omar Sandoval <osandov@...ndov.com>
Cc: Chris Mason <clm@...com>, Josef Bacik <jbacik@...com>,
linux-btrfs@...r.kernel.org, Josh Triplett <josh@...htriplett.org>,
Steven Rostedt <rostedt@...dmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Lai Jiangshan <laijs@...fujitsu.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] Move BTRFS RCU string to common library
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@...ux.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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists