From: "Huang\, Ying" <ying.huang@intel.com>
To: Wanpeng Li <wanpeng.li@hotmail.com>
Cc: 0day robot <fengguang.wu@intel.com>, <lkp@01.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [lkp] [KVM] 0c32e5dd82: stderr: KVM: entry failed, hardware error 0x80000021
Date: Tue, 10 Nov 2015 13:29:27 +0800 [thread overview]
Message-ID: <87pozibex4.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <BLU436-SMTP1470E0609C9AAB5FE767A3080140@phx.gbl> (Wanpeng Li's message of "Tue, 10 Nov 2015 13:22:04 +0800")
Wanpeng Li <wanpeng.li@hotmail.com> writes:
> On 11/10/15 9:47 AM, kernel test robot wrote:
>> FYI, we noticed the below changes on
>>
>> https://github.com/0day-ci/linux Wanpeng-Li/KVM-x86-Reset-RFLAGS-state-following-processor-init-reset/20151103-194355
>> commit 0c32e5dd82fd0e63fd9e6aecf5a4bffbdf2ab207 ("KVM: x86: Reset RFLAGS state following processor init/reset")
>>
>> The stderr of kvm-unit-tests is as follow for your commit.
>
> Thanks for the report, however, I don't think maintainer pick this
> patch in any tree currently, which tree you are testing against?
We test patches from LKML directly now :)
Best Regards,
Huang, Ying
WARNING: multiple messages have this Message-ID (diff)
From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [KVM] 0c32e5dd82: stderr: KVM: entry failed, hardware error 0x80000021
Date: Tue, 10 Nov 2015 13:29:27 +0800 [thread overview]
Message-ID: <87pozibex4.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <BLU436-SMTP1470E0609C9AAB5FE767A3080140@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
Wanpeng Li <wanpeng.li@hotmail.com> writes:
> On 11/10/15 9:47 AM, kernel test robot wrote:
>> FYI, we noticed the below changes on
>>
>> https://github.com/0day-ci/linux Wanpeng-Li/KVM-x86-Reset-RFLAGS-state-following-processor-init-reset/20151103-194355
>> commit 0c32e5dd82fd0e63fd9e6aecf5a4bffbdf2ab207 ("KVM: x86: Reset RFLAGS state following processor init/reset")
>>
>> The stderr of kvm-unit-tests is as follow for your commit.
>
> Thanks for the report, however, I don't think maintainer pick this
> patch in any tree currently, which tree you are testing against?
We test patches from LKML directly now :)
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2015-11-10 5:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 1:47 [lkp] [KVM] 0c32e5dd82: stderr: KVM: entry failed, hardware error 0x80000021 kernel test robot
2015-11-10 1:47 ` kernel test robot
2015-11-10 5:22 ` Wanpeng Li
2015-11-10 5:29 ` Huang, Ying [this message]
2015-11-10 5:29 ` Huang, Ying
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=87pozibex4.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=wanpeng.li@hotmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.