From: Colin Ian King <colin.i.king@gmail.com>
To: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Filipe Manana <fdmanana@suse.com>,
linux-btrfs@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH][next] btrfs: selftests: Fix spelling mistake "suceeded" -> "succeeded"
Date: Mon, 13 Jan 2025 09:18:46 +0000 [thread overview]
Message-ID: <20250113091846.23813-1-colin.i.king@gmail.com> (raw)
There is a spelling mistake in two test_err messages. Fix them.
Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
---
fs/btrfs/tests/raid-stripe-tree-tests.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/btrfs/tests/raid-stripe-tree-tests.c b/fs/btrfs/tests/raid-stripe-tree-tests.c
index 6c7e561e5564..6747350a05f5 100644
--- a/fs/btrfs/tests/raid-stripe-tree-tests.c
+++ b/fs/btrfs/tests/raid-stripe-tree-tests.c
@@ -315,7 +315,7 @@ static int test_delete_two_extents(struct btrfs_trans_handle *trans)
ret = btrfs_get_raid_extent_offset(fs_info, logical1, &len1, map_type,
0, &io_stripe);
if (ret != -ENODATA) {
- test_err("lookup of RAID extent [%llu, %llu] suceeded, should fail\n",
+ test_err("lookup of RAID extent [%llu, %llu] succeeded, should fail\n",
logical1, len1);
goto out;
}
@@ -323,7 +323,7 @@ static int test_delete_two_extents(struct btrfs_trans_handle *trans)
ret = btrfs_get_raid_extent_offset(fs_info, logical2, &len2, map_type,
0, &io_stripe);
if (ret != -ENODATA) {
- test_err("lookup of RAID extent [%llu, %llu] suceeded, should fail\n",
+ test_err("lookup of RAID extent [%llu, %llu] succeeded, should fail\n",
logical2, len2);
goto out;
}
--
2.47.1
next reply other threads:[~2025-01-13 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 9:18 Colin Ian King [this message]
2025-01-13 11:30 ` Johannes Thumshirn
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=20250113091846.23813-1-colin.i.king@gmail.com \
--to=colin.i.king@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--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
all inboxes | Powered by JetHome®