From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/5] KVM: Add kvm_vmx01 to the runtest file
Date: Wed, 16 Apr 2025 08:19:58 +0200 [thread overview]
Message-ID: <20250416061958.GA560513@pevik> (raw)
In-Reply-To: <20250407142351.25900-3-mdoucha@suse.cz>
Hi Martin,
This and previous patch as obvious fixes merged.
Thanks!
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-04-16 6:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 14:23 [LTP] [PATCH 0/5] KVM test for Intel VMX vAPIC Martin Doucha
2025-04-07 14:23 ` [LTP] [PATCH 1/5] kvm_vmx01: Fix 32bit compiler warnings Martin Doucha
2025-04-07 14:23 ` [LTP] [PATCH 2/5] KVM: Add kvm_vmx01 to the runtest file Martin Doucha
2025-04-16 6:19 ` Petr Vorel [this message]
2025-04-07 14:23 ` [LTP] [PATCH 3/5] KVM: Simplify reading VMX control field masks Martin Doucha
2025-04-16 6:22 ` Petr Vorel
2025-04-16 7:16 ` Petr Vorel
2025-04-28 10:38 ` Martin Doucha
2025-04-28 12:29 ` Petr Vorel
2025-04-07 14:23 ` [LTP] [PATCH 4/5] KVM: Add constants for Intel VMX vAPIC control Martin Doucha
2025-04-16 6:24 ` Petr Vorel
2025-04-07 14:23 ` [LTP] [PATCH 5/5] Add test for Intel VMX virtualized APIC Martin Doucha
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=20250416061958.GA560513@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/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