mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v2] ver_linux: add missing software to checklist
Date: Tue, 31 Jan 2023 13:07:42 -0700	[thread overview]
Message-ID: <cc2c8b52-43ce-48a0-600b-ada5fd67b8b8@linuxfoundation.org> (raw)
In-Reply-To: <CAJ1xhMU3CPK9nLyx0ejqMt6KKcaeewsstQzUA7KKExumJ7hYzQ@mail.gmail.com>

On 1/26/23 01:02, Alexander Kapshuk wrote:
> On Tue, Jan 24, 2023 at 11:04 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>
>> ---
>> Changes since v1: addressed review comments
>>
>>   scripts/ver_linux | 28 ++++++++++++++++++++++++----
>>   1 file changed, 24 insertions(+), 4 deletions(-)
>>
>> diff --git a/scripts/ver_linux b/scripts/ver_linux
>> index 1a8ee4ff0e32..2daee7e88c45 100755
>> --- a/scripts/ver_linux
>> +++ b/scripts/ver_linux
>> @@ -6,20 +6,29 @@
>>   # 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
> 
> The usage message is followed by three new line characters, the 1st is
> embedded in the last line of the usage message, the second is output
> by the print function, and the third by the leading new line character
> in the separator string.
> All other sections use two trailing new line characters instead.
> If the formatting of this section is desired to be consistent with all
> the other sections, this print function may be substituted with the
> printf function, which does not append a new line character to its
> argument.
> 

> 
> Other than that, LGTM. Thanks.

Thanks for checking this. Make sense to keep it consistent. Will
fix it in the next version.

thanks,
-- Shuah


      reply	other threads:[~2023-01-31 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 20:43 Shuah Khan
2023-01-26  8:02 ` Alexander Kapshuk
2023-01-31 20:07   ` 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=cc2c8b52-43ce-48a0-600b-ada5fd67b8b8@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

all inboxes | Powered by JetHome®