From: Shuah Khan <skhan@linuxfoundation.org>
To: Alexander Kapshuk <alexander.kapshuk@gmail.com>
Cc: linux-kernel@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] ver_linux: add missing software to checklist
Date: Fri, 20 Jan 2023 14:06:31 -0700 [thread overview]
Message-ID: <2f6561ac-ac1d-7689-c0a4-83cf412ee66c@linuxfoundation.org> (raw)
In-Reply-To: <CAJ1xhMXtRUnLJQKkPyUemLpYiAP4ebmgExS6cV2Kta6rCd__0w@mail.gmail.com>
On 1/16/23 05:26, Alexander Kapshuk wrote:
> On Tue, Jan 10, 2023 at 11:13 PM Shuah Khan <skhan@linuxfoundation.org> wrote:
>>
>> Update to add missing software checks to bring it in sync with the
>> Documentation/Changes list. Make improvements to the output with
>> separator between different sections.
>>
>> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
>> ---
>> scripts/ver_linux | 29 ++++++++++++++++++++++++++---
>> 1 file changed, 26 insertions(+), 3 deletions(-)
>>
>> diff --git a/scripts/ver_linux b/scripts/ver_linux
>> index 1a8ee4ff0e32..6131f6f1b35b 100755
>> --- a/scripts/ver_linux
>> +++ b/scripts/ver_linux
>> @@ -6,10 +6,14 @@
>> # differ on your system.
>>
>> BEGIN {
>> - usage = "If some fields are empty or look unusual you may have an old version.\n"
>> - usage = usage "Compare to the current minimal requirements in Documentation/Changes.\n"
>> + usage = "Minimum required software versions to build and run current kernel version.\n"
>> + usage = usage "If some fields are empty or look unusual you may have an old version.\n"
>> + usage = usage "Compare with the current minimal requirements in Documentation/Changes.\n"
>> print usage
>>
>> + separator = "===================================================\n"
>
> Embedding a new line character at the start of the separator string
> would eliminate the need for the extra printf("\n") statements
> introduced.
>
>> +
>> + print separator
>> system("uname -a")
>> printf("\n")
>
> Consequently, this printf could be removed as well.
>
Thank yo for your review. Will send v2 with your suggestions.
thanks,
-- Shuah
prev parent reply other threads:[~2023-01-20 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 20:42 [PATCH] ver_linux: add missing software to checklist Shuah Khan
2023-01-10 22:45 ` Bhaskar Chowdhury
2023-01-10 23:25 ` Shuah Khan
2023-01-16 12:26 ` Alexander Kapshuk
2023-01-20 21:06 ` Shuah Khan [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=2f6561ac-ac1d-7689-c0a4-83cf412ee66c@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=alexander.kapshuk@gmail.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).