qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Konstantin Kostiuk <konstantin@daynix.com>,
	Developers <qemu-devel@nongnu.org>
Cc: Michael Roth <michael.roth@amd.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [PATCH] qga-win: Add support of Windows Server 2022 in get-osinfo command
Date: Wed, 28 Jul 2021 13:57:36 +0200	[thread overview]
Message-ID: <2ca6c79c-ab03-e361-0efb-e1d232e89835@redhat.com> (raw)
In-Reply-To: <CAJ28CFQsv7HN5HemsiXByz0zPAPfpuYYyzkNBUN6cyV22vW6qQ@mail.gmail.com>

On 7/28/21 9:53 AM, Konstantin Kostiuk wrote:
> ping

Seems merged:

commit c141814d4f495bd9efdabb1229ce0a5b5a239bf3
Author: Kostiantyn Kostiuk <konstantin@daynix.com>
Date:   Mon Jun 21 15:50:17 2021 +0300

    qga-win: Add support of Windows Server 2022 in get-osinfo command

    Signed-off-by: Kostiantyn Kostiuk <konstantin@daynix.com>
    Signed-off-by: Michael Roth <michael.roth@amd.com>

> On Wed, Jul 14, 2021 at 10:25 AM Konstantin Kostiuk
> <konstantin@daynix.com <mailto:konstantin@daynix.com>> wrote:
> 
> 
>     ping
> 
> 
>     On Sun, Jul 11, 2021 at 8:18 PM Konstantin Kostiuk
>     <konstantin@daynix.com <mailto:konstantin@daynix.com>> wrote:
> 
>         ping
> 
>         On Sun, Jul 4, 2021 at 8:51 AM Konstantin Kostiuk
>         <konstantin@daynix.com <mailto:konstantin@daynix.com>> wrote:
> 
>             ping
> 
>             On Mon, Jun 21, 2021 at 3:50 PM Kostiantyn Kostiuk
>             <konstantin@daynix.com <mailto:konstantin@daynix.com>> wrote:
> 
>                 Signed-off-by: Kostiantyn Kostiuk <konstantin@daynix.com
>                 <mailto:konstantin@daynix.com>>
>                 ---
>                  qga/commands-win32.c | 3 ++-
>                  1 file changed, 2 insertions(+), 1 deletion(-)
> 
>                 diff --git a/qga/commands-win32.c b/qga/commands-win32.c
>                 index 300b87c859..93b08fd4b5 100644
>                 --- a/qga/commands-win32.c
>                 +++ b/qga/commands-win32.c
>                 @@ -2209,9 +2209,10 @@ typedef struct
>                 _ga_win_10_0_server_t {
>                      char const *version_id;
>                  } ga_win_10_0_server_t;
> 
>                 -static ga_win_10_0_server_t const
>                 WIN_10_0_SERVER_VERSION_MATRIX[3] = {
>                 +static ga_win_10_0_server_t const
>                 WIN_10_0_SERVER_VERSION_MATRIX[4] = {
>                      {14393, "Microsoft Windows Server 2016",    "2016"},
>                      {17763, "Microsoft Windows Server 2019",    "2019"},
>                 +    {20344, "Microsoft Windows Server 2022",    "2022"},
>                      {0, 0}
>                  };
> 
>                 --
>                 2.25.1
> 



      reply	other threads:[~2021-07-28 11:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 12:50 [PATCH] qga-win: Add support of Windows Server 2022 in get-osinfo command Kostiantyn Kostiuk
2021-07-04  5:51 ` Konstantin Kostiuk
2021-07-11 17:18   ` Konstantin Kostiuk
2021-07-14  7:25     ` Konstantin Kostiuk
2021-07-28  7:53       ` Konstantin Kostiuk
2021-07-28 11:57         ` Philippe Mathieu-Daudé [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=2ca6c79c-ab03-e361-0efb-e1d232e89835@redhat.com \
    --to=philmd@redhat.com \
    --cc=konstantin@daynix.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=michael.roth@amd.com \
    --cc=qemu-devel@nongnu.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).