All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Daniel Rosenberg <drosen@google.com>,
	Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-f2fs-devel@lists.sourceforge.net
Cc: linux-doc@vger.kernel.org, linux-api@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	kernel-team@android.com
Subject: Re: [f2fs-dev] [PATCH v4 1/3] fs: Reserve flag for casefolding
Date: Sun, 28 Jul 2019 08:36:11 +0800	[thread overview]
Message-ID: <056a12d4-d787-9a3d-9ad4-4d1136b2a197@kernel.org> (raw)
In-Reply-To: <20190723230529.251659-2-drosen@google.com>

On 2019-7-24 7:05, Daniel Rosenberg via Linux-f2fs-devel wrote:
> 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>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,

WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: Daniel Rosenberg <drosen@google.com>,
	Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-f2fs-devel@lists.sourceforge.net
Cc: linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
	kernel-team@android.com, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v4 1/3] fs: Reserve flag for casefolding
Date: Sun, 28 Jul 2019 08:36:11 +0800	[thread overview]
Message-ID: <056a12d4-d787-9a3d-9ad4-4d1136b2a197@kernel.org> (raw)
In-Reply-To: <20190723230529.251659-2-drosen@google.com>

On 2019-7-24 7:05, Daniel Rosenberg via Linux-f2fs-devel wrote:
> 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>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2019-07-28  0:36 UTC|newest]

Thread overview: 32+ 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 ` [f2fs-dev] " Daniel Rosenberg via Linux-f2fs-devel
2019-07-23 23:05 ` [PATCH v4 1/3] fs: Reserve flag for casefolding Daniel Rosenberg
2019-07-23 23:05   ` [f2fs-dev] " Daniel Rosenberg via Linux-f2fs-devel
2019-07-28  0:36   ` Chao Yu [this message]
2019-07-28  0:36     ` Chao Yu
2019-07-23 23:05 ` [PATCH v4 2/3] f2fs: include charset encoding information in the superblock Daniel Rosenberg
2019-07-23 23:05   ` [f2fs-dev] " Daniel Rosenberg via Linux-f2fs-devel
2019-07-23 23:05   ` Daniel Rosenberg
2019-07-28  0:45   ` [f2fs-dev] " Chao Yu
2019-07-28  0:45     ` Chao Yu
2019-07-23 23:05 ` [PATCH v4 3/3] f2fs: Support case-insensitive file name lookups Daniel Rosenberg
2019-07-23 23:05   ` [f2fs-dev] " Daniel Rosenberg via Linux-f2fs-devel
2019-07-28  0:55   ` Chao Yu
2019-07-28  0:55     ` Chao Yu
2019-07-28  0:55     ` Chao Yu
2019-07-29  6:27     ` [f2fs-dev] " Jaegeuk Kim
2019-07-29  6:27       ` Jaegeuk Kim
2019-07-29  7:22       ` Chao Yu
2019-07-29  7:22         ` Chao Yu
2019-07-29  7:22         ` Chao Yu
2019-07-29 14:57         ` Chao Yu
2019-07-29 14:57           ` Chao Yu
2019-07-31 17:57   ` Nathan Chancellor
2019-07-31 17:57     ` [f2fs-dev] " Nathan Chancellor
2019-08-01  1:11     ` Chao Yu
2019-08-01  1:11       ` [f2fs-dev] " Chao Yu
2019-08-01  1:11       ` Chao Yu
2019-08-01  4:05       ` Jaegeuk Kim
2019-08-01  4:05         ` [f2fs-dev] " Jaegeuk Kim
2019-08-21 13:15   ` Chao Yu
2019-08-21 13:15     ` 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=056a12d4-d787-9a3d-9ad4-4d1136b2a197@kernel.org \
    --to=chao@kernel.org \
    --cc=corbet@lwn.net \
    --cc=drosen@google.com \
    --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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.