From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Sync inode flags with ext2.
Date: Thu, 23 Sep 2010 14:23:35 -0700 [thread overview]
Message-ID: <20100923212335.GD6609@mail.oracle.com> (raw)
In-Reply-To: <1284874949-3352-2-git-send-email-tao.ma@oracle.com>
On Sun, Sep 19, 2010 at 01:42:29PM +0800, Tao Ma wrote:
> We sync our inode flags with ext2 and define them by hex
> values. But actually in commit 3669567(4 years ago), all
> these values are moved to include/linux/fs.h. So we'd
> better also use them as what ext2 did. So sync our inode
> flags with ext2 by using FS_*.
>
> Signed-off-by: Tao Ma <tao.ma@oracle.com>
This patch is now in the 'fixes' branch of ocfs2.git.
Joel
--
"The cynics are right nine times out of ten."
- H. L. Mencken
Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-09-23 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 5:42 [Ocfs2-devel] [PATCH v2] ocfs2: Move 'wanted' into parens of ocfs2_resmap_resv_bits Tao Ma
2010-09-19 5:42 ` [Ocfs2-devel] [PATCH] ocfs2: Sync inode flags with ext2 Tao Ma
2010-09-23 21:23 ` Joel Becker [this message]
2010-09-23 21:23 ` [Ocfs2-devel] [PATCH v2] ocfs2: Move 'wanted' into parens of ocfs2_resmap_resv_bits Joel Becker
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=20100923212335.GD6609@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.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).