From: Greg KH <gregkh@linuxfoundation.org>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, apw@canonical.com, jasowang@redhat.com
Subject: Re: [PATCH 1/1] tools: hv: Return the full kernel version
Date: Sat, 13 Oct 2012 15:44:35 +0900 [thread overview]
Message-ID: <20121013064435.GA9794@kroah.com> (raw)
In-Reply-To: <1350085210-11108-1-git-send-email-kys@microsoft.com>
On Fri, Oct 12, 2012 at 04:40:10PM -0700, K. Y. Srinivasan wrote:
> Currently, we are returning the same string for both OSBuildNumber
> and OSVersion keys. Return the full uts string for the OSBuild
> key since Windows does not impose any restrictions on this.
You sent me 2 patches, both 1/1, that modify the same file. Which one
comes first? Please resend both properly, and also let me know if these
are things that should be going into 3.7 or can wait for 3.8.
greg k-h
next prev parent reply other threads:[~2012-10-13 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 23:40 [PATCH 1/1] tools: hv: Return the full kernel version K. Y. Srinivasan
2012-10-13 6:44 ` Greg KH [this message]
2012-10-13 16:03 ` KY Srinivasan
2012-10-13 17:28 ` Greg KH
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=20121013064435.GA9794@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
/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