From: Josef Bacik <jbacik@fusionio.com>
To: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
Cc: Josef Bacik <jbacik@fusionio.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: fix send to deal with sparse files properly V2
Date: Fri, 30 Aug 2013 08:24:24 -0400 [thread overview]
Message-ID: <20130830122424.GG10591@localhost.localdomain> (raw)
In-Reply-To: <5220003F.6090103@cn.fujitsu.com>
On Fri, Aug 30, 2013 at 10:15:27AM +0800, Wang Shilong wrote:
> On 08/22/2013 11:47 PM, Josef Bacik wrote:
>
> please use checkpatch.pl to check coding styles before sending patches:
>
> WARNING: line over 80 characters
> #86: FILE: fs/btrfs/send.c:4051:
> + if (btrfs_file_extent_disk_bytenr(path->nodes[0], ei) == 0) {
>
> total: 0 errors, 1 warnings, 59 lines checked
>
Yeah I did that on purpose, thanks,
Josef
prev parent reply other threads:[~2013-08-30 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 15:47 [PATCH] Btrfs: fix send to deal with sparse files properly V2 Josef Bacik
2013-08-30 2:15 ` Wang Shilong
2013-08-30 12:24 ` Josef Bacik [this message]
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=20130830122424.GG10591@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangsl.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).