- Break up the ksft_print_msg statements to follow the 80 char rule.
- Capitalize "POSIX" and rephrase messages for better readability.
- Clarify that false negatives may occur in tests relying on timers
  if other threads run on the CPU.

Signed-off-by: I Viswanath <viswanathiyyappan@gmail.com>
---
 tools/testing/selftests/timers/posix_timers.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/tools/testing/selftests/timers/posix_timers.c b/tools/testing/selftests/timers/posix_timers.c
index f0eceb0faf34..017a9e19ad0f 100644
--- a/tools/testing/selftests/timers/posix_timers.c
+++ b/tools/testing/selftests/timers/posix_timers.c
@@ -673,8 +673,9 @@ int main(int argc, char **argv)
 	ksft_print_header();
 	ksft_set_plan(19);
 
-	ksft_print_msg("Testing posix timers. False negative may happen on CPU execution \n");
-	ksft_print_msg("based timers if other threads run on the CPU...\n");
+	ksft_print_msg("Testing POSIX timers.\n");
+	ksft_print_msg("False negatives may occur in tests\n");
+	ksft_print_msg("relying on timers if other threads run on the CPU\n");
 
 	check_timer_create_exact();
 
-- 
2.50.1