From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Zhiguo Niu <zhiguo.niu@unisoc.com>, jaegeuk@kernel.org
Cc: Hao_hao.Wang@unisoc.com, ke.wang@unisoc.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: remove redundant atomic file check in defragment
Date: Thu, 31 Oct 2024 15:52:17 +0800 [thread overview]
Message-ID: <8b06aaba-e626-4b9a-9963-85ad8b89c866@kernel.org> (raw)
In-Reply-To: <1730354393-19672-1-git-send-email-zhiguo.niu@unisoc.com>
On 2024/10/31 13:59, Zhiguo Niu wrote:
> f2fs_is_atomic_file(inode) is checked in f2fs_defragment_range,
> so remove the redundant checking in f2fs_ioc_defragment.
>
> Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.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
next prev parent reply other threads:[~2024-10-31 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 5:59 [f2fs-dev] [PATCH 1/2] f2fs: remove redundant atomic file check in defragment Zhiguo Niu
2024-10-31 5:59 ` [f2fs-dev] [PATCH 2/2] f2fs: fix to adjust appropriate length for fiemap Zhiguo Niu
2024-11-01 2:36 ` Chao Yu via Linux-f2fs-devel
2024-11-01 3:27 ` Zhiguo Niu
2024-11-01 5:48 ` Zhiguo Niu
2024-11-01 8:00 ` Zhiguo Niu
2024-10-31 7:52 ` Chao Yu via Linux-f2fs-devel [this message]
2024-11-07 20:30 ` [f2fs-dev] [PATCH 1/2] f2fs: remove redundant atomic file check in defragment patchwork-bot+f2fs--- via Linux-f2fs-devel
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=8b06aaba-e626-4b9a-9963-85ad8b89c866@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=Hao_hao.Wang@unisoc.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=ke.wang@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zhiguo.niu@unisoc.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.