All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Fasheh <mfasheh@suse.com>, Joel Becker <jlbec@evilplan.org>,
	linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 2/2] ocfs2: Neaten do_error, ocfs2_error and ocfs2_abort
Date: Fri, 27 Mar 2015 16:04:04 -0700	[thread overview]
Message-ID: <1427497444.24954.1.camel@perches.com> (raw)
In-Reply-To: <20150327151610.bcc26d7577d35ce636d21833@linux-foundation.org>

On Fri, 2015-03-27 at 15:16 -0700, Andrew Morton wrote:
> On Thu, 26 Mar 2015 20:07:08 -0700 Joe Perches <joe@perches.com> wrote:
> 
> > These uses sometimes do and sometimes don't have '\n' terminations.
> > Make the uses consistently use '\n' terminations and remove the
> > newline from the functions.
> 
> This is going to take a while to merge, as it's backed up behind a pile
> of needs-more-reviewing ocfs2 patches.

Thanks, no worries, this one's a trivial neatening patch.

WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Fasheh <mfasheh@suse.com>, Joel Becker <jlbec@evilplan.org>,
	linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [PATCH 2/2] ocfs2: Neaten do_error, ocfs2_error and ocfs2_abort
Date: Fri, 27 Mar 2015 16:04:04 -0700	[thread overview]
Message-ID: <1427497444.24954.1.camel@perches.com> (raw)
In-Reply-To: <20150327151610.bcc26d7577d35ce636d21833@linux-foundation.org>

On Fri, 2015-03-27 at 15:16 -0700, Andrew Morton wrote:
> On Thu, 26 Mar 2015 20:07:08 -0700 Joe Perches <joe@perches.com> wrote:
> 
> > These uses sometimes do and sometimes don't have '\n' terminations.
> > Make the uses consistently use '\n' terminations and remove the
> > newline from the functions.
> 
> This is going to take a while to merge, as it's backed up behind a pile
> of needs-more-reviewing ocfs2 patches.

Thanks, no worries, this one's a trivial neatening patch.


  reply	other threads:[~2015-03-27 23:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27  3:07 [Ocfs2-devel] [PATCH 0/2] ocfs2: logging neatening Joe Perches
2015-03-27  3:07 ` Joe Perches
2015-03-27  3:07 ` [Ocfs2-devel] [PATCH 1/2] ocfs2: Logging: Remove static buffer, use vsprintf extension %pV Joe Perches
2015-03-27  3:07   ` Joe Perches
2015-03-27  3:07 ` [Ocfs2-devel] [PATCH 2/2] ocfs2: Neaten do_error, ocfs2_error and ocfs2_abort Joe Perches
2015-03-27  3:07   ` Joe Perches
2015-03-27 22:16   ` [Ocfs2-devel] " Andrew Morton
2015-03-27 22:16     ` Andrew Morton
2015-03-27 23:04     ` Joe Perches [this message]
2015-03-27 23:04       ` Joe Perches

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=1427497444.24954.1.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=jlbec@evilplan.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfasheh@suse.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.