From: patchwork-bot+f2fs@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 1/2] f2fs: fix to update i_ctime in __f2fs_setxattr()
Date: Mon, 14 Aug 2023 20:50:22 +0000 [thread overview]
Message-ID: <169204622223.5033.2752517082147339614.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230719135047.2947030-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 19 Jul 2023 21:50:45 +0800 you wrote:
> generic/728 - output mismatch (see /media/fstests/results//generic/728.out.bad)
> --- tests/generic/728.out 2023-07-19 07:10:48.362711407 +0000
> +++ /media/fstests/results//generic/728.out.bad 2023-07-19 08:39:57.000000000 +0000
> QA output created by 728
> +Expected ctime to change after setxattr.
> +Expected ctime to change after removexattr.
> Silence is golden
> ...
> (Run 'diff -u /media/fstests/tests/generic/728.out /media/fstests/results//generic/728.out.bad' to see the entire diff)
> generic/729 1s
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: fix to update i_ctime in __f2fs_setxattr()
https://git.kernel.org/jaegeuk/f2fs/c/8874ad7dae8d
- [f2fs-dev,2/2] f2fs: remove unneeded check condition in __f2fs_setxattr()
https://git.kernel.org/jaegeuk/f2fs/c/bc3994ffa4cf
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-14 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 13:50 [PATCH 1/2] f2fs: fix to update i_ctime in __f2fs_setxattr() Chao Yu
2023-07-19 13:50 ` [PATCH 2/2] f2fs: remove unneeded check condition " Chao Yu
2023-08-14 20:50 ` patchwork-bot+f2fs [this message]
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=169204622223.5033.2752517082147339614.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox