From: Chao Yu <chao@kernel.org>
To: Zhiguo Niu <zhiguo.niu@unisoc.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, niuzhiguo84@gmail.com,
ke.wang@unisoc.com, Hao_hao.Wang@unisoc.com
Subject: Re: [PATCH 2/2] f2fs: fix to correct check conditions in f2fs_cross_rename
Date: Fri, 23 May 2025 10:11:40 +0800 [thread overview]
Message-ID: <4aeeec81-63ec-4991-b6b5-9091c67178eb@kernel.org> (raw)
In-Reply-To: <1747212349-18425-2-git-send-email-zhiguo.niu@unisoc.com>
On 5/14/25 16:45, Zhiguo Niu wrote:
> Should be "old_dir" here.
>
> Fixes: 5c57132eaf52 ("f2fs: support project quota")
> Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2025-05-23 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 8:45 [PATCH 1/2] f2fs: use d_inode(dentry) cleanup dentry->d_inode Zhiguo Niu
2025-05-14 8:45 ` [PATCH 2/2] f2fs: fix to correct check conditions in f2fs_cross_rename Zhiguo Niu
2025-05-23 2:11 ` Chao Yu [this message]
2025-05-23 2:10 ` [PATCH 1/2] f2fs: use d_inode(dentry) cleanup dentry->d_inode Chao Yu
2025-05-28 16:20 ` [f2fs-dev] " 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=4aeeec81-63ec-4991-b6b5-9091c67178eb@kernel.org \
--to=chao@kernel.org \
--cc=Hao_hao.Wang@unisoc.com \
--cc=jaegeuk@kernel.org \
--cc=ke.wang@unisoc.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=niuzhiguo84@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox