From: Anand Jain <Anand.Jain@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs-progs: add correct indentation
Date: Thu, 28 Feb 2013 09:52:48 +0800 [thread overview]
Message-ID: <512EB870.6050600@oracle.com> (raw)
In-Reply-To: <20130227154504.GH27541@twin.jikos.cz>
On 02/27/2013 11:45 PM, David Sterba wrote:
> On Fri, Feb 22, 2013 at 02:59:24PM +0800, Anand Jain wrote:
>> --- a/utils.c
>> +++ b/utils.c
>> @@ -1192,12 +1192,13 @@ scan_again:
>> return -ENOENT;
>> }
>> /* skip the header */
>> - for(i=0; i < 2 ; i++)
>> - if(!fgets(buf, 1023, proc_partitions)){
>> - fprintf(stderr, "Unable to read '/proc/partitions' for scanning\n");
>> - fclose(proc_partitions);
>> - return -ENOENT;
>> - }
>> + for (i=0; i < 2 ; i++)
>
> for (i = 0; i < 2; i++)
>
> If possible, It's good to fix these issues in one go, I'll fix it locally.
Absolutely. Sorry my mistake. A new patch below if it helps. Thanks
Anand
prev parent reply other threads:[~2013-02-28 1:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 6:59 [PATCH] Btrfs-progs: add correct indentation Anand Jain
2013-02-27 15:45 ` David Sterba
2013-02-28 1:52 ` Anand Jain [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=512EB870.6050600@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.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).