linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: liubo <liubo2009@cn.fujitsu.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org, jim owens <owens6336@gmail.com>,
	Chris Mason <chris.mason@oracle.com>,
	"Yan, Zheng" <zheng.yan@oracle.com>
Subject: Re: [PATCH] btrfs/direct-IO: fix a bug of btrfs_dio_read
Date: Thu, 06 May 2010 10:24:39 +0800	[thread overview]
Message-ID: <4BE22867.5080204@cn.fujitsu.com> (raw)
In-Reply-To: <20100506021136.GB5672@localhost.localdomain>

On 05/06/2010 10:11 AM, Josef Bacik wrote:
>
> Please read my previous email, DIO has been refactored, this code isn't going to
> be used anymore.  Thanks,
>
> Josef
>
>
>   

All right, I'll look into new DIO. :-)

Thanks,
LiuBo


      reply	other threads:[~2010-05-06  2:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  2:12 [PATCH] btrfs/direct-IO: fix a bug of btrfs_dio_read liubo
2010-05-06  2:11 ` Josef Bacik
2010-05-06  2:24   ` liubo [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=4BE22867.5080204@cn.fujitsu.com \
    --to=liubo2009@cn.fujitsu.com \
    --cc=chris.mason@oracle.com \
    --cc=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=owens6336@gmail.com \
    --cc=zheng.yan@oracle.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 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).