From: Daniel Rosenberg <drosen@google.com> To: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>, Jonathan Corbet <corbet@lwn.net>, linux-f2fs-devel@lists.sourceforge.net Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org, kernel-team@android.com, Daniel Rosenberg <drosen@google.com> Subject: [PATCH v4 1/3] fs: Reserve flag for casefolding Date: Tue, 23 Jul 2019 16:05:27 -0700 [thread overview] Message-ID: <20190723230529.251659-2-drosen@google.com> (raw) In-Reply-To: <20190723230529.251659-1-drosen@google.com> In preparation for including the casefold feature within f2fs, elevate the EXT4_CASEFOLD_FL flag to FS_CASEFOLD_FL. Signed-off-by: Daniel Rosenberg <drosen@google.com> --- include/uapi/linux/fs.h | 1 + tools/include/uapi/linux/fs.h | 1 + 2 files changed, 2 insertions(+) diff --git a/include/uapi/linux/fs.h b/include/uapi/linux/fs.h index 59c71fa8c553a..2a616aa3f6862 100644 --- a/include/uapi/linux/fs.h +++ b/include/uapi/linux/fs.h @@ -311,6 +311,7 @@ struct fscrypt_key { #define FS_NOCOW_FL 0x00800000 /* Do not cow file */ #define FS_INLINE_DATA_FL 0x10000000 /* Reserved for ext4 */ #define FS_PROJINHERIT_FL 0x20000000 /* Create with parents projid */ +#define FS_CASEFOLD_FL 0x40000000 /* Folder is case insensitive */ #define FS_RESERVED_FL 0x80000000 /* reserved for ext2 lib */ #define FS_FL_USER_VISIBLE 0x0003DFFF /* User visible flags */ diff --git a/tools/include/uapi/linux/fs.h b/tools/include/uapi/linux/fs.h index 59c71fa8c553a..2a616aa3f6862 100644 --- a/tools/include/uapi/linux/fs.h +++ b/tools/include/uapi/linux/fs.h @@ -311,6 +311,7 @@ struct fscrypt_key { #define FS_NOCOW_FL 0x00800000 /* Do not cow file */ #define FS_INLINE_DATA_FL 0x10000000 /* Reserved for ext4 */ #define FS_PROJINHERIT_FL 0x20000000 /* Create with parents projid */ +#define FS_CASEFOLD_FL 0x40000000 /* Folder is case insensitive */ #define FS_RESERVED_FL 0x80000000 /* reserved for ext2 lib */ #define FS_FL_USER_VISIBLE 0x0003DFFF /* User visible flags */ -- 2.22.0.657.g960e92d24f-goog
next prev parent reply other threads:[~2019-07-23 23:07 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-23 23:05 [PATCH v4 0/3] Casefolding in F2FS Daniel Rosenberg 2019-07-23 23:05 ` Daniel Rosenberg [this message] 2019-07-28 0:36 ` [f2fs-dev] [PATCH v4 1/3] fs: Reserve flag for casefolding Chao Yu 2019-07-23 23:05 ` [PATCH v4 2/3] f2fs: include charset encoding information in the superblock Daniel Rosenberg 2019-07-28 0:45 ` [f2fs-dev] " Chao Yu 2019-07-23 23:05 ` [PATCH v4 3/3] f2fs: Support case-insensitive file name lookups Daniel Rosenberg 2019-07-28 0:55 ` [f2fs-dev] " Chao Yu 2019-07-29 6:27 ` Jaegeuk Kim 2019-07-29 7:22 ` Chao Yu 2019-07-29 14:57 ` Chao Yu 2019-07-31 17:57 ` Nathan Chancellor 2019-08-01 1:11 ` Chao Yu 2019-08-01 4:05 ` Jaegeuk Kim 2019-08-21 13:15 ` [f2fs-dev] " Chao Yu
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=20190723230529.251659-2-drosen@google.com \ --to=drosen@google.com \ --cc=corbet@lwn.net \ --cc=jaegeuk@kernel.org \ --cc=kernel-team@android.com \ --cc=linux-api@vger.kernel.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-f2fs-devel@lists.sourceforge.net \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=yuchao0@huawei.com \ --subject='Re: [PATCH v4 1/3] fs: Reserve flag for casefolding' \ /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
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).