Linux ocfs2 filesystem development
 help / color / mirror / Atom feed
From: Younger Liu <younger.liu@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [V2, RESENT] ocfs2: lighten up allocate transaction
Date: Tue, 3 Sep 2013 10:51:53 +0800	[thread overview]
Message-ID: <52254EC9.7020106@huawei.com> (raw)
In-Reply-To: <5222d9d9.9mQfRonnYwCLHx6n%wangshilong1991@gmail.com>

On 2013/9/1 14:08, Wang Shilong wrote:
> Hello, Using checkpatch.pl, i get the following warnings(errors):
> ERROR: patch seems to be corrupt (line wrapped?)
> #57: FILE: fs/ocfs2/file.c:665:
> 		} else {
> 
> total: 1 errors, 0 warnings, 87 lines checked
> 
> patch has style problems, please review.  If any of these errors
> are false positives report them to the maintainer, see
> CHECKPATCH in MAINTAINERS.
> 
> Thanks, Wang
> 
> 
Thanks for your review.
  I reviewed the patch again. The patch is not the newest one. 
I have sent patch V3. So I will sent patch V3 again.
	--Younger

           reply	other threads:[~2013-09-03  2:51 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5222d9d9.9mQfRonnYwCLHx6n%wangshilong1991@gmail.com>]

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=52254EC9.7020106@huawei.com \
    --to=younger.liu@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox