From: Chao Yu <chao@kernel.org>
To: Sheng Yong <shengyong@oppo.com>, jaegeuk@kernel.org
Cc: ebiggers@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v4 2/6] f2fs: cleanup MIN_INLINE_XATTR_SIZE
Date: Tue, 13 Jun 2023 09:48:34 +0800 [thread overview]
Message-ID: <45faec38-aeaf-d89e-4542-e87e5edc049a@kernel.org> (raw)
In-Reply-To: <20230612030121.2393541-3-shengyong@oppo.com>
On 2023/6/12 11:01, Sheng Yong wrote:
> Signed-off-by: Sheng Yong <shengyong@oppo.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
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: Chao Yu <chao@kernel.org>
To: Sheng Yong <shengyong@oppo.com>, jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, ebiggers@kernel.org
Subject: Re: [PATCH v4 2/6] f2fs: cleanup MIN_INLINE_XATTR_SIZE
Date: Tue, 13 Jun 2023 09:48:34 +0800 [thread overview]
Message-ID: <45faec38-aeaf-d89e-4542-e87e5edc049a@kernel.org> (raw)
In-Reply-To: <20230612030121.2393541-3-shengyong@oppo.com>
On 2023/6/12 11:01, Sheng Yong wrote:
> Signed-off-by: Sheng Yong <shengyong@oppo.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2023-06-13 1:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 3:01 [f2fs-dev] [PATCH v4 0/6] f2fs: add f2fs_ioc_[get|set]_extra_attr Sheng Yong via Linux-f2fs-devel
2023-06-12 3:01 ` Sheng Yong
2023-06-12 3:01 ` [f2fs-dev] [PATCH v4 1/6] f2fs: add helper to check compression level Sheng Yong via Linux-f2fs-devel
2023-06-12 3:01 ` Sheng Yong
2023-06-12 22:14 ` [f2fs-dev] " Jaegeuk Kim
2023-06-12 22:14 ` Jaegeuk Kim
2023-06-13 1:48 ` [f2fs-dev] " Chao Yu
2023-06-13 1:48 ` Chao Yu
2023-06-13 2:28 ` [f2fs-dev] " Sheng Yong via Linux-f2fs-devel
2023-06-13 2:28 ` Sheng Yong
2023-06-12 3:01 ` [f2fs-dev] [PATCH v4 2/6] f2fs: cleanup MIN_INLINE_XATTR_SIZE Sheng Yong via Linux-f2fs-devel
2023-06-12 3:01 ` Sheng Yong
2023-06-13 1:48 ` Chao Yu [this message]
2023-06-13 1:48 ` Chao Yu
2023-06-12 3:01 ` [f2fs-dev] [PATCH v4 3/6] f2fs: add helper to get inode chksum from inode page Sheng Yong via Linux-f2fs-devel
2023-06-12 3:01 ` Sheng Yong
2023-06-13 1:52 ` [f2fs-dev] " Chao Yu
2023-06-13 1:52 ` Chao Yu
2023-06-12 3:01 ` [f2fs-dev] [PATCH v4 4/6] f2fs: add f2fs_ioc_get_compress_blocks Sheng Yong via Linux-f2fs-devel
2023-06-12 3:01 ` Sheng Yong
2023-06-13 1:53 ` [f2fs-dev] " Chao Yu
2023-06-13 1:53 ` Chao Yu
2023-06-12 3:01 ` [f2fs-dev] [PATCH v4 5/6] f2fs: add f2fs_ioc_[get|set]_extra_attr Sheng Yong via Linux-f2fs-devel
2023-06-12 3:01 ` Sheng Yong
2023-06-12 15:47 ` [f2fs-dev] " Jaegeuk Kim
2023-06-12 15:47 ` Jaegeuk Kim
2023-06-13 1:53 ` [f2fs-dev] " Sheng Yong via Linux-f2fs-devel
2023-06-13 1:53 ` Sheng Yong
2023-06-12 3:01 ` [f2fs-dev] [PATCH v4 6/6] f2fs: access compression level and flags by extra attr ioctls Sheng Yong via Linux-f2fs-devel
2023-06-12 3:01 ` Sheng Yong
2023-06-15 18:00 ` [f2fs-dev] [PATCH v4 0/6] f2fs: add f2fs_ioc_[get|set]_extra_attr patchwork-bot+f2fs
2023-06-15 18:00 ` patchwork-bot+f2fs
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=45faec38-aeaf-d89e-4542-e87e5edc049a@kernel.org \
--to=chao@kernel.org \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shengyong@oppo.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.