From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: Anand Jain <Anand.Jain@oracle.com>
Cc: Wang Shilong <wangshilong1991@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs-progs: v3, move out print in cmd_df to another function
Date: Mon, 02 Sep 2013 11:00:52 +0800 [thread overview]
Message-ID: <5223FF64.8030805@cn.fujitsu.com> (raw)
In-Reply-To: <5223FECB.3010601@oracle.com>
On 09/02/2013 10:58 AM, Anand Jain wrote:
>
> Wang, kindly note that this was fixed in v4.
Yeah...This is sent by my shell script by accident, I have fixed it and
it won't send the repeated message again.
Thanks for reminding .. ^_^
>
> Anand
>
>
> On 09/01/2013 02:15 PM, Wang Shilong wrote:
>> Hello, Using checkpatch.pl, i get the following warnings(errors):
>> ERROR: "foo * bar" should be "foo *bar"
>> #37: FILE: cmds-filesystem.c:47:
>> +static char * group_type_str(u64 flag)
>>
>> ERROR: "foo * bar" should be "foo *bar"
>> #69: FILE: cmds-filesystem.c:63:
>> +static char * group_profile_str(u64 flag)
>>
>> total: 2 errors, 0 warnings, 229 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
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-btrfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2013-09-02 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 6:15 btrfs-progs: v3, move out print in cmd_df to another function Wang Shilong
2013-09-02 2:58 ` Anand Jain
2013-09-02 3:00 ` Wang Shilong [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=5223FF64.8030805@cn.fujitsu.com \
--to=wangsl.fnst@cn.fujitsu.com \
--cc=Anand.Jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangshilong1991@gmail.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.