linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: miaox@cn.fujitsu.com
Cc: Chris Mason <chris.mason@oracle.com>,
	Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 01/10] btrfs: add a return value for readahead_tree_block()
Date: Wed, 02 Jun 2010 11:07:38 +0800	[thread overview]
Message-ID: <4C05CAFA.9000700@cn.fujitsu.com> (raw)
In-Reply-To: <4BF4E12F.6010103@cn.fujitsu.com>

Hi, Chris

Could you review this patchset for us? 

Regards
Miao


on 2010-5-20 15:13, Miao Xie wrote:
> From: Liu Bo <liubo2009@cn.fujitsu.com>
> 
> Fix return value to get from read_extent_buffer_pages().
> 
> Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com>
> Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
> ---
>  fs/btrfs/disk-io.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index 6632e5c..35916d5 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -794,7 +794,7 @@ int readahead_tree_block(struct btrfs_root *root, u64 bytenr, u32 blocksize,
>  	buf = btrfs_find_create_tree_block(root, bytenr, blocksize);
>  	if (!buf)
>  		return 0;
> -	read_extent_buffer_pages(&BTRFS_I(btree_inode)->io_tree,
> +	ret = read_extent_buffer_pages(&BTRFS_I(btree_inode)->io_tree,
>  				 buf, 0, 0, btree_get_extent, 0);
>  	free_extent_buffer(buf);
>  	return ret;



      reply	other threads:[~2010-06-02  3:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20  7:13 [PATCH 01/10] btrfs: add a return value for readahead_tree_block() Miao Xie
2010-06-02  3:07 ` Miao Xie [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=4C05CAFA.9000700@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=chris.mason@oracle.com \
    --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).