[PATCH] fstests: add commit IDs for kernel fixes already merged

[email protected]
Newsgroups org.kernel.vger.fstests,org.kernel.vger.linux-btrfs
Message-ID <db06887383a2a3d34801de9fb180241157177204.1777910956.git.fdmanana@suse.com>
From: Filipe Manana <[email protected]>

A few fixes were merged into Linus' tree, so add their commit IDs in the
respective test cases.

Signed-off-by: Filipe Manana <[email protected]>
---
 tests/btrfs/343   | 2 +-
 tests/btrfs/344   | 4 ++--
 tests/generic/792 | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/tests/btrfs/343 b/tests/btrfs/343
index 53e6028b..fd38c010 100755
--- a/tests/btrfs/343
+++ b/tests/btrfs/343
@@ -13,7 +13,7 @@ _begin_fstest auto quick compress
 _require_scratch
 _require_btrfs_command inspect-internal dump-tree
 
-_fixed_by_kernel_commit xxxxxxxxxxxx \
+_fixed_by_kernel_commit 883adb6dcff0 \
 	"btrfs: fix the inline compressed extent check in inode_need_compress()"
 
 _scratch_mkfs >>$seqres.full 2>&1
diff --git a/tests/btrfs/344 b/tests/btrfs/344
index 932b20d4..6e5d38d6 100755
--- a/tests/btrfs/344
+++ b/tests/btrfs/344
@@ -13,8 +13,8 @@ _begin_fstest auto quick compress
 _require_scratch
 _require_btrfs_command inspect-internal dump-tree
 
-_fixed_by_kernel_commit xxxxxxxxxxxx \
-	"btrfs: do not mark inode incompressible after inline attempt failed"
+_fixed_by_kernel_commit 2e0e3716c7b6 \
+	"btrfs: do not mark inode incompressible after inline attempt fails"
 
 _scratch_mkfs >>$seqres.full 2>&1
 
diff --git a/tests/generic/792 b/tests/generic/792
index 892ca2d8..d1896728 100755
--- a/tests/generic/792
+++ b/tests/generic/792
@@ -25,7 +25,7 @@ _require_scratch
 _require_test_program unlink-fsync
 _require_dm_target flakey
 
-_fixed_by_fs_commit btrfs xxxxxxxxxxxx \
+_fixed_by_fs_commit btrfs 999757231c49 \
 	"btrfs: fix missing last_unlink_trans update when removing a directory"
 
 _scratch_mkfs >> $seqres.full 2>&1 || _fail "mkfs failed"
-- 
2.47.2
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.