public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Kapshuk <alexander.kapshuk@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: Subject: [PATCH] ver_linux: uniform output across various linux distros
Date: Mon, 28 Sep 2015 07:09:44 -0700	[thread overview]
Message-ID: <20150928140944.GB20559@kroah.com> (raw)
In-Reply-To: <CAJ1xhMUE=CMrxnrzKWD_M5n0Qh04bYQ-ToojU6tHfKUDcviCvg@mail.gmail.com>

On Mon, Sep 28, 2015 at 07:50:37AM +0300, Alexander Kapshuk wrote:
> Hello,

Hi!

First off, your Subject: is a bit odd, you might want to fix up your
email client :)

> 
> Having run 'scripts/ver_linux' on my Gentoo system, as well as having
> looked through some recent bug reports on the kernel bugzilla website
> showing the output of the script in question, I have observed that
> the output is not accurate across various distros. While the current
> implementation of the script expects the version info to be found in
> particular fields, some of the utilities invoked by the script, output
> their version information in varying formats, which results in the
> script displaying information other than the version number.
> 
> The proposed implementation relies mostly on sed to detect the version
> numbers more accurately. Running the patched version of the script on
> the distros below resulted in accurate and uniform output.
> 
> Gentoo Linux
> Debian 6.0.10
> Oracle Linux Server release 7.1
> Arch Linux
> 
> The items left unchanged are those I did not have access to. I would
> be willing to work on those too, if supplied the output of the affected
> commands whose format differs based on the distro.

<snip>

Your patch is a bit complex, you are changing the formatting, and at the
same time, also changing the code.  Please do this in multiple patches,
one to fix any issues you see, and the second to then clean up the
formatting, making it easier to actually see what the difference is
here.

Also, take a look at Documentation/SubmittingPatches for the proper
format of a kernel patch to ensure we are able to accept it (hint, your
patch is missing the signed-off-by line in the body of the changelog
area).

thanks,

greg k-h

  reply	other threads:[~2015-09-28 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28  4:50 Subject: [PATCH] ver_linux: uniform output across various linux distros Alexander Kapshuk
2015-09-28 14:09 ` Greg KH [this message]
2015-09-28 21:56 ` Randy Dunlap
2015-09-29  4:44   ` Alexander Kapshuk

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=20150928140944.GB20559@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.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