public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: linux@leemhuis.info, rdunlap@infradead.org
Cc: linux-kernel@vger.kernel.org, Bhaskar Chowdhury <unixbhaskar@gmail.com>
Subject: [PATCH] rearrange the output text, cosmetic changes
Date: Tue, 24 Mar 2020 14:15:13 +0530	[thread overview]
Message-ID: <20200324084513.18237-1-unixbhaskar@gmail.com> (raw)

As the subject like says, purely cosmetic changes to read cleanly.
Jumbled up the line.

Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
 tools/debugging/kernel-chktaint | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/tools/debugging/kernel-chktaint b/tools/debugging/kernel-chktaint
index 2240cb56e6e5..74fd3282aa1b 100755
--- a/tools/debugging/kernel-chktaint
+++ b/tools/debugging/kernel-chktaint
@@ -195,8 +195,9 @@ else
 	echo " * kernel was built with the struct randomization plugin (#17)"
 fi

-echo "For a more detailed explanation of the various taint flags see"
-echo " Documentation/admin-guide/tainted-kernels.rst in the the Linux kernel sources"
-echo " or https://kernel.org/doc/html/latest/admin-guide/tainted-kernels.html"
 echo "Raw taint value as int/string: $taint/'$out'"
+echo
+echo "For a more detailed explanation of the various taint flags see below pointers:"
+echo "1) Documentation/admin-guide/tainted-kernels.rst in  the Linux kernel sources"
+echo "2)  https://kernel.org/doc/html/latest/admin-guide/tainted-kernels.html"
 #EOF#
--
2.24.1


             reply	other threads:[~2020-03-24  8:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24  8:45 Bhaskar Chowdhury [this message]
2020-03-24 15:15 ` [PATCH] rearrange the output text, cosmetic changes Joe Perches
2020-03-24 22:29   ` Bhaskar Chowdhury

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=20200324084513.18237-1-unixbhaskar@gmail.com \
    --to=unixbhaskar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=rdunlap@infradead.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