linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhao Lei <zhaolei@cn.fujitsu.com>
To: <dsterba@suse.cz>
Cc: "'Chris Mason'" <clm@fb.com>, "'btrfs'" <linux-btrfs@vger.kernel.org>
Subject: RE: [GIT PULL] Fujitsu for 4.5
Date: Mon, 18 Jan 2016 19:02:27 +0800	[thread overview]
Message-ID: <020901d151df$b81250e0$2836f2a0$@cn.fujitsu.com> (raw)
In-Reply-To: <20160115164943.GF4227@twin.jikos.cz>

Hi, David Sterba

> From: David Sterba [mailto:dsterba@suse.cz]
> Sent: Saturday, January 16, 2016 12:50 AM
> To: Zhao Lei <zhaolei@cn.fujitsu.com>
> Cc: dsterba@suse.cz; 'Chris Mason' <clm@fb.com>; 'btrfs'
> <linux-btrfs@vger.kernel.org>
> Subject: Re: [GIT PULL] Fujitsu for 4.5
> 
> On Fri, Jan 15, 2016 at 05:46:42PM +0800, Zhao Lei wrote:
> > And following 3 patchs in this branch are also for readahead, but
> > sorry that I forgot adding "reada" prefix in subject.
> >   btrfs: Fix in-segment calculation for reada
> >   btrfs: reduce additional fs_info->reada_lock in reada_find_zone
> >   btrfs: Add missed segment checking in reada_find_zone
> >
> > Would you please consider helping me to review them?
> 
> All three reviewed and look ok, but the changelogs could be improved, eg. what
> are the implications of missing the zones etc.

Thanks for review.
I'll update changelogs in the tree.

Thanks
Zhaolei




  reply	other threads:[~2016-01-18 11:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13  9:28 [GIT PULL] Fujitsu for 4.5 Zhao Lei
2016-01-14 14:17 ` David Sterba
2016-01-15  9:46   ` Zhao Lei
2016-01-15 16:49     ` David Sterba
2016-01-18 11:02       ` Zhao Lei [this message]
2016-01-15 16:12   ` Chris Mason
2016-02-10 10:13 ` David Sterba
2016-02-15  4:07   ` Zhao Lei
2016-02-16 10:05     ` 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='020901d151df$b81250e0$2836f2a0$@cn.fujitsu.com' \
    --to=zhaolei@cn.fujitsu.com \
    --cc=clm@fb.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).