public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: linux@leemhuis.info, rdunlap@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rearrange the output text, cosmetic changes
Date: Wed, 25 Mar 2020 03:59:46 +0530	[thread overview]
Message-ID: <20200324222943.GA18504@Gentoo> (raw)
In-Reply-To: <fb5a17c67f504f5761069ee446cc1b703dd8b54f.camel@perches.com>

[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]

On 08:15 Tue 24 Mar 2020, Joe Perches wrote:
>On Tue, 2020-03-24 at 14:15 +0530, Bhaskar Chowdhury wrote:
>> As the subject like says, purely cosmetic changes to read cleanly.
>> Jumbled up the line.
>
>Subject line should show tools or kernel-chktaint
>
>and:
>
>> diff --git 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"
>
>One extra space between "in  the"
>
>

Thanks, Joe ...fixing! next patch should have fixed them.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2020-03-24 22:30 UTC|newest]

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

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=20200324222943.GA18504@Gentoo \
    --to=unixbhaskar@gmail.com \
    --cc=joe@perches.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