From: Colin Ian King <colin.i.king@gmail.com>
To: "Shuah Khan" <shuah@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Christoph Müllner" <christoph.muellner@vrull.eu>,
linux-kselftest@vger.kernel.org, linux-riscv@lists.infradead.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH][next] tools: selftests: riscv: Fix spelling mistake "regesters" -> "registers"
Date: Mon, 29 Jul 2024 10:17:34 +0100 [thread overview]
Message-ID: <20240729091734.42259-1-colin.i.king@gmail.com> (raw)
There are a couple of spelling mistakes in ksft_test_result_fail messages.
Fix them.
Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
---
tools/testing/selftests/riscv/vector/v_initval_nolibc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/riscv/vector/v_initval_nolibc.c b/tools/testing/selftests/riscv/vector/v_initval_nolibc.c
index 1dd94197da30..6838c561e4c9 100644
--- a/tools/testing/selftests/riscv/vector/v_initval_nolibc.c
+++ b/tools/testing/selftests/riscv/vector/v_initval_nolibc.c
@@ -49,14 +49,14 @@ int main(void)
ksft_print_msg("vl = %lu\n", vl);
if (datap[0] != 0x00 && datap[0] != 0xff) {
- ksft_test_result_fail("v-regesters are not properly initialized\n");
+ ksft_test_result_fail("v-registers are not properly initialized\n");
dump(datap, vl * 4);
exit(-1);
}
for (i = 1; i < vl * 4; i++) {
if (datap[i] != datap[0]) {
- ksft_test_result_fail("detect stale values on v-regesters\n");
+ ksft_test_result_fail("detect stale values on v-registers\n");
dump(datap, vl * 4);
exit(-2);
}
--
2.39.2
next reply other threads:[~2024-07-29 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 9:17 Colin Ian King [this message]
2024-07-29 21:57 ` [PATCH][next] tools: selftests: riscv: Fix spelling mistake "regesters" -> "registers" Charlie Jenkins
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=20240729091734.42259-1-colin.i.king@gmail.com \
--to=colin.i.king@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=christoph.muellner@vrull.eu \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=shuah@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