From: Eric Biggers <ebiggers@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: introduce f2fs_casefold_name slab cache
Date: Thu, 10 Jun 2021 15:57:27 -0700 [thread overview]
Message-ID: <YMKY11PC5y/EfZYf@gmail.com> (raw)
In-Reply-To: <20210608000022.5509-1-chao@kernel.org>
On Tue, Jun 08, 2021 at 08:00:22AM +0800, Chao Yu wrote:
> From: Chao Yu <yuchao0@huawei.com>
>
> Add a slab cache: "f2fs_casefold_name" for memory allocation
> of casefold name.
Commit message should say "f2fs_casefolded_name", not "f2fs_casefold_name".
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> ---
> v2:
> - change slab cache name to "f2fs_casefolded_name"
> - add a "f2fs_" prefix for slab cache variable name
> fs/f2fs/dir.c | 17 +++++++++++------
> fs/f2fs/recovery.c | 6 +++++-
> fs/f2fs/super.c | 24 ++++++++++++++++++++++++
Otherwise this looks good.
Reviewed-by: Eric Biggers <ebiggers@google.com>
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: introduce f2fs_casefold_name slab cache
Date: Thu, 10 Jun 2021 15:57:27 -0700 [thread overview]
Message-ID: <YMKY11PC5y/EfZYf@gmail.com> (raw)
In-Reply-To: <20210608000022.5509-1-chao@kernel.org>
On Tue, Jun 08, 2021 at 08:00:22AM +0800, Chao Yu wrote:
> From: Chao Yu <yuchao0@huawei.com>
>
> Add a slab cache: "f2fs_casefold_name" for memory allocation
> of casefold name.
Commit message should say "f2fs_casefolded_name", not "f2fs_casefold_name".
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> ---
> v2:
> - change slab cache name to "f2fs_casefolded_name"
> - add a "f2fs_" prefix for slab cache variable name
> fs/f2fs/dir.c | 17 +++++++++++------
> fs/f2fs/recovery.c | 6 +++++-
> fs/f2fs/super.c | 24 ++++++++++++++++++++++++
Otherwise this looks good.
Reviewed-by: Eric Biggers <ebiggers@google.com>
- Eric
next prev parent reply other threads:[~2021-06-10 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 0:00 [f2fs-dev] [PATCH v2] f2fs: introduce f2fs_casefold_name slab cache Chao Yu
2021-06-08 0:00 ` Chao Yu
2021-06-10 22:57 ` Eric Biggers [this message]
2021-06-10 22:57 ` [f2fs-dev] " Eric Biggers
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=YMKY11PC5y/EfZYf@gmail.com \
--to=ebiggers@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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.