From: Chao Yu <chao@kernel.org>
To: Zorro Lang <zlang@kernel.org>, fstests@vger.kernel.org
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
Chao Yu <chao@kernel.org>
Subject: [PATCH 2/3] f2fs/006: update commit id in _fixed_by_kernel_commit line
Date: Mon, 2 Dec 2024 19:41:48 +0800 [thread overview]
Message-ID: <20241202114149.2666-2-chao@kernel.org> (raw)
In-Reply-To: <20241202114149.2666-1-chao@kernel.org>
The bug related to this regression testcase has been fixed by commit
1acd73edbbfe ("f2fs: fix to account dirty data in __get_secs_required()"),
let's update commit id in _fixed_by_kernel_commit line.
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Signed-off-by: Chao Yu <chao@kernel.org>
---
tests/f2fs/006 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/f2fs/006 b/tests/f2fs/006
index a9c823c1..c1f8d4ff 100755
--- a/tests/f2fs/006
+++ b/tests/f2fs/006
@@ -16,7 +16,7 @@
. ./common/preamble
_begin_fstest auto quick
-_fixed_by_kernel_commit xxxxxxxxxxxx \
+_fixed_by_kernel_commit 1acd73edbbfe \
"f2fs: fix to account dirty data in __get_secs_required()"
_require_scratch
--
2.40.1
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Zorro Lang <zlang@kernel.org>, fstests@vger.kernel.org
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 2/3] f2fs/006: update commit id in _fixed_by_kernel_commit line
Date: Mon, 2 Dec 2024 19:41:48 +0800 [thread overview]
Message-ID: <20241202114149.2666-2-chao@kernel.org> (raw)
In-Reply-To: <20241202114149.2666-1-chao@kernel.org>
The bug related to this regression testcase has been fixed by commit
1acd73edbbfe ("f2fs: fix to account dirty data in __get_secs_required()"),
let's update commit id in _fixed_by_kernel_commit line.
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Signed-off-by: Chao Yu <chao@kernel.org>
---
tests/f2fs/006 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/f2fs/006 b/tests/f2fs/006
index a9c823c1..c1f8d4ff 100755
--- a/tests/f2fs/006
+++ b/tests/f2fs/006
@@ -16,7 +16,7 @@
. ./common/preamble
_begin_fstest auto quick
-_fixed_by_kernel_commit xxxxxxxxxxxx \
+_fixed_by_kernel_commit 1acd73edbbfe \
"f2fs: fix to account dirty data in __get_secs_required()"
_require_scratch
--
2.40.1
_______________________________________________
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-12-02 11:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 11:41 [PATCH 1/3] f2fs/005: update commit id in _fixed_by_kernel_commit line Chao Yu
2024-12-02 11:41 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2024-12-02 11:41 ` Chao Yu [this message]
2024-12-02 11:41 ` [f2fs-dev] [PATCH 2/3] f2fs/006: " Chao Yu via Linux-f2fs-devel
2024-12-02 11:41 ` [PATCH 3/3] f2fs/007: " Chao Yu
2024-12-02 11:41 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2024-12-02 19:28 ` [PATCH 1/3] f2fs/005: " Zorro Lang
2024-12-02 19:28 ` [f2fs-dev] " Zorro Lang
2024-12-03 11:29 ` Chao Yu
2024-12-03 11:29 ` [f2fs-dev] " Chao Yu 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=20241202114149.2666-2-chao@kernel.org \
--to=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=zlang@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.