From: vivekyadav1207731111@gmail.com
To: catalin.marinas@arm.com, will@kernel.org, shuah@kernel.org,
corbet@lwn.net
Cc: linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-doc@vger.kernel.org,
Vivek Yadav <vivekyadav1207731111@gmail.com>
Subject: [PATCH 2/3] kselftest/arm64: Supress warning and improve readability
Date: Sat, 23 Aug 2025 23:14:01 -0700 [thread overview]
Message-ID: <20250824061402.13432-3-vivekyadav1207731111@gmail.com> (raw)
In-Reply-To: <20250824061402.13432-1-vivekyadav1207731111@gmail.com>
From: Vivek Yadav <vivekyadav1207731111@gmail.com>
The comment was correct, but `checkpatch` script flagged it with a warning
as shown in the output section. The comment is slightly modified
to improve readability, which also suppresses the warning.
```
[command]
./script/checkpatch.pl --strict -f tools/testing/selftests/arm64/fp/fp-stress.c
[output]
WARNING: Possible repeated word: 'on'
```
Fixes: 98102a2cb7860 : kselftest/arm64: Hold fp-stress children until they're all spawned.
Signed-off-by: Vivek Yadav <vivekyadav1207731111@gmail.com>
---
tools/testing/selftests/arm64/fp/fp-stress.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/arm64/fp/fp-stress.c b/tools/testing/selftests/arm64/fp/fp-stress.c
index 74e23208b94c..3a0ae96cf909 100644
--- a/tools/testing/selftests/arm64/fp/fp-stress.c
+++ b/tools/testing/selftests/arm64/fp/fp-stress.c
@@ -105,8 +105,8 @@ static void child_start(struct child_data *child, const char *program)
/*
* Read from the startup pipe, there should be no data
- * and we should block until it is closed. We just
- * carry on on error since this isn't super critical.
+ * and we should block until it is closed. We just
+ * carry-on on error since this isn't super critical.
*/
ret = read(3, &i, sizeof(i));
if (ret < 0)
--
2.25.1
next prev parent reply other threads:[~2025-08-24 6:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 6:13 [PATCH 0/3] kselftest/arm64: Cleanups and readability fixes vivekyadav1207731111
2025-08-24 6:14 ` [PATCH 1/3] kselftest/arm64: Remove extra blank line vivekyadav1207731111
2025-08-24 6:14 ` vivekyadav1207731111 [this message]
2025-08-24 6:14 ` [PATCH 3/3] kselftest/arm64: Add parentheses around sizeof for clarity vivekyadav1207731111
2025-09-08 15:55 ` [PATCH 0/3] kselftest/arm64: Cleanups and readability fixes Will Deacon
-- strict thread matches above, loose matches on Subject: below --
2025-08-17 5:25 vivekyadav1207731111
2025-08-17 5:25 ` [PATCH 2/3] kselftest/arm64: Supress warning and improve readability vivekyadav1207731111
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=20250824061402.13432-3-vivekyadav1207731111@gmail.com \
--to=vivekyadav1207731111@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=will@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®