linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhao Lei <zhaolei@cn.fujitsu.com>
To: "'Dan Carpenter'" <dan.carpenter@oracle.com>
Cc: <linux-btrfs@vger.kernel.org>, "'David Sterba'" <dsterba@suse.cz>
Subject: RE: btrfs: reada: simplify dev->reada_in_flight processing
Date: Thu, 18 Feb 2016 09:37:41 +0800	[thread overview]
Message-ID: <007601d169ec$f5d23f10$e176bd30$@cn.fujitsu.com> (raw)
In-Reply-To: <20160217190152.GA10246@mwanda>

Hi, Dan Carpenter

> From: Dan Carpenter [mailto:dan.carpenter@oracle.com]
> Sent: Thursday, February 18, 2016 3:02 AM
> To: zhaolei@cn.fujitsu.com
> Cc: linux-btrfs@vger.kernel.org
> Subject: re: btrfs: reada: simplify dev->reada_in_flight processing
> 
> Hello Zhao Lei,
> 
> The patch 7aff519c04d2: "btrfs: reada: simplify dev->reada_in_flight
> processing" from Jan 12, 2016, leads to the following static checker
> warning:
> 
> 	fs/btrfs/reada.c:697 reada_start_machine_dev()
> 	warn: inconsistent indenting
> 
> fs/btrfs/reada.c
>    688                  spin_unlock(&fs_info->reada_lock);
>    689                  return 0;
>    690          }
>    691          dev->reada_next = re->logical +
> fs_info->tree_root->nodesize;
>    692          re->refcnt++;
>    693
>    694          spin_unlock(&fs_info->reada_lock);
>    695
>    696          spin_lock(&re->lock);
>    697                  if (re->scheduled || list_empty(&re->extctl)) {
> 
> This is indented too much.
> 
Thanks for report.

This problem is introduced in patch titled:
btrfs: reada: Move is_need_to_readahead contition earlier

I'll fix it.

CC: David Sterba <dsterba@suse.cz>
I'll fix this indent problem in following branch:
https://github.com/zhaoleidd/btrfs.git integration-4.5

Could you pick them again?

Thanks
Zhaolei

>    698                          spin_unlock(&re->lock);
>    699                          reada_extent_put(fs_info, re);
>    700                          return 0;
>    701                  }
>    702                  re->scheduled = 1;
>    703          spin_unlock(&re->lock);
>    704
> 
> regards,
> dan carpenter





  reply	other threads:[~2016-02-18  1:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 19:01 btrfs: reada: simplify dev->reada_in_flight processing Dan Carpenter
2016-02-18  1:37 ` Zhao Lei [this message]
2016-02-18  9:39   ` David Sterba

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='007601d169ec$f5d23f10$e176bd30$@cn.fujitsu.com' \
    --to=zhaolei@cn.fujitsu.com \
    --cc=dan.carpenter@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).