From: Chris Mason <chris.mason@oracle.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] fs: remove FS_COW_FL
Date: Tue, 03 May 2011 07:20:11 -0400 [thread overview]
Message-ID: <1304421568-sup-4709@think> (raw)
In-Reply-To: <4DBFC6D0.3010105@cn.fujitsu.com>
Excerpts from Li Zefan's message of 2011-05-03 05:11:44 -0400:
> Any comments? If this patch is acceptable, it should be queued for .39?
> since fs.h is exported to userspace.
>
> Li Zefan wrote:
> > FS_COW_FL and FS_NOCOW_FL were newly introduced to control per file
> > COW in btrfs, but FS_NOCOW_FL is sufficient.
> >
Good point, I'll send this in.
-chris
prev parent reply other threads:[~2011-05-03 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 3:02 [PATCH 1/3] fs: remove FS_COW_FL Li Zefan
2011-04-15 3:03 ` [PATCH 2/3] Btrfs: fix FS_IOC_GETFLAGS ioctl Li Zefan
2011-04-15 3:03 ` [PATCH 3/3] Btrfs: fix FS_IOC_SETFLAGS ioctl Li Zefan
2011-05-03 9:11 ` [PATCH 1/3] fs: remove FS_COW_FL Li Zefan
2011-05-03 11:20 ` Chris Mason [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=1304421568-sup-4709@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.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).