From: Konstantin Kostiuk <konstantin@daynix.com>
To: Developers <qemu-devel@nongnu.org>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [PATCH] qga-win: Add support of Windows Server 2022 in get-osinfo command
Date: Sun, 4 Jul 2021 08:51:36 +0300 [thread overview]
Message-ID: <CAJ28CFSxqVawommAhzH+Fu++Xf4gtQdBQCZ6mHGVpTi6qUK2MA@mail.gmail.com> (raw)
In-Reply-To: <20210621125017.113989-1-konstantin@daynix.com>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
ping
On Mon, Jun 21, 2021 at 3:50 PM Kostiantyn Kostiuk <konstantin@daynix.com>
wrote:
> Signed-off-by: Kostiantyn Kostiuk <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
>
[-- Attachment #2: Type: text/html, Size: 1390 bytes --]
next prev parent reply other threads:[~2021-07-04 5:52 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 [this message]
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é
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=CAJ28CFSxqVawommAhzH+Fu++Xf4gtQdBQCZ6mHGVpTi6qUK2MA@mail.gmail.com \
--to=konstantin@daynix.com \
--cc=mdroth@linux.vnet.ibm.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).