From: Abdelrahman Fekry <abdelrahmanfekry375@gmail.com>
To: shuah@kernel.org, skhan@linuxfoundation.org
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev,
Abdelrahman Fekry <abdelrahmanfekry375@gmail.com>
Subject: [PATCH v2] selftests: size: fix grammar and align output formatting
Date: Fri, 23 May 2025 05:05:11 +0300 [thread overview]
Message-ID: <20250523020511.10306-1-abdelrahmanfekry375@gmail.com> (raw)
This is v2 of the patch.
The Signed-off-by line mismatch reported by checkpatch
has been fixed.
Improve the grammar in the test name by changing "get runtime memory use"
to "get runtime memory usage". Also adjust spacing in output lines
("Total:", "Free:", etc.) to ensure consistent alignment and readability.
Signed-off-by: Abdelrahman Fekry <abdelrahmanfekry375@gmail.com>
---
tools/testing/selftests/size/get_size.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tools/testing/selftests/size/get_size.c b/tools/testing/selftests/size/get_size.c
index 2980b1a63366..d5b67c073d8e 100644
--- a/tools/testing/selftests/size/get_size.c
+++ b/tools/testing/selftests/size/get_size.c
@@ -86,7 +86,7 @@ void _start(void)
int ccode;
struct sysinfo info;
unsigned long used;
- static const char *test_name = " get runtime memory use\n";
+ static const char *test_name = " get runtime memory usage\n";
print("TAP version 13\n");
print("# Testing system size.\n");
@@ -105,8 +105,8 @@ void _start(void)
used = info.totalram - info.freeram - info.bufferram;
print("# System runtime memory report (units in Kilobytes):\n");
print(" ---\n");
- print_k_value(" Total: ", info.totalram, info.mem_unit);
- print_k_value(" Free: ", info.freeram, info.mem_unit);
+ print_k_value(" Total : ", info.totalram, info.mem_unit);
+ print_k_value(" Free : ", info.freeram, info.mem_unit);
print_k_value(" Buffer: ", info.bufferram, info.mem_unit);
print_k_value(" In use: ", used, info.mem_unit);
print(" ...\n");
--
2.25.1
reply other threads:[~2025-05-23 2:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250523020511.10306-1-abdelrahmanfekry375@gmail.com \
--to=abdelrahmanfekry375@gmail.com \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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