linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Joe Perches <joe@perches.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
	linux-btrfs@vger.kernel.org,
	"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
Subject: Re: [PATCH v3 1/2] Return a value from printk_ratelimited
Date: Sat, 27 Sep 2014 00:45:59 -0700	[thread overview]
Message-ID: <20140927074559.GA30196@molino.home.network> (raw)
In-Reply-To: <1411796891.21874.14.camel@joe-AO725>

On Fri, Sep 26, 2014 at 10:48:11PM -0700, Joe Perches wrote:
> I'd prefer to keep it the way it is actually.
> 
> I've submitted several patches to convert the int return
> to void for printk derived functions recently.

Alright, it doesn't seem like anyone feels strongly for keeping the return
values, so I'll go ahead and submit a v4 that doesn't modify printk_ratelimited
and doesn't return anything from the printk functions in rcustring.h unless
there are any objections.

-- 
Omar

  reply	other threads:[~2014-09-27  7:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-27  5:36 [PATCH v3 0/2] Move BTRFS RCU string to common library Omar Sandoval
2014-09-27  5:36 ` [PATCH v3 1/2] Return a value from printk_ratelimited Omar Sandoval
2014-09-27  5:48   ` Joe Perches
2014-09-27  7:45     ` Omar Sandoval [this message]
2014-09-27  5:36 ` [PATCH v3 2/2] Move BTRFS RCU string to common library Omar Sandoval
2014-09-27  5:46 ` [PATCH v3 0/2] " 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=20140927074559.GA30196@molino.home.network \
    --to=osandov@osandov.com \
    --cc=clm@fb.com \
    --cc=jbacik@fb.com \
    --cc=joe@perches.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=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).