From: "\"“tiejun.chen”\"" <tiejun.chen@windriver.com>
To: Scott Wood <scottwood@freescale.com>
Cc: <agraf@suse.de>, <kvm@vger.kernel.org>, <kvm-ppc@vger.kernel.org>
Subject: Re: [PATCH 1/2] Revert "kvm/ppc/booke64: Fix lazy ee handling in kvmppc_handle_exit()"
Date: Wed, 7 Aug 2013 09:58:40 +0800 [thread overview]
Message-ID: <5201A9D0.1090406@windriver.com> (raw)
In-Reply-To: <1375822238.5600.16.camel@snotra.buserror.net>
On 08/07/2013 04:50 AM, Scott Wood wrote:
> On Tue, 2013-08-06 at 17:31 +0800, Tiejun Chen wrote:
>> We should revert this commit to rework.
>>
>> Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
>
> This breaks bisect.
Hmm...
Maybe I can squash these two patches into one.
Tiejun
next prev parent reply other threads:[~2013-08-07 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 9:31 [PATCH 0/2] KVM: PPC: Book3E HV: Rework to sync the software state Tiejun Chen
2013-08-06 9:31 ` [PATCH 1/2] Revert "kvm/ppc/booke64: Fix lazy ee handling in kvmppc_handle_exit()" Tiejun Chen
2013-08-06 20:50 ` Scott Wood
2013-08-07 1:58 ` "“tiejun.chen”" [this message]
2013-08-06 9:31 ` [PATCH 2/2] KVM: PPC: Book3E HV: call SOFT_DISABLE_INTS to sync the software state Tiejun Chen
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=5201A9D0.1090406@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=scottwood@freescale.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 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).