From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Alexander Graf <agraf@suse.de>
Cc: Scott Wood <scottwood@freescale.com>,
Gleb Natapov <gleb@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Mihai Caraman <mihai.caraman@freescale.com>,
"<kvm-ppc@vger.kernel.org>" <kvm-ppc@vger.kernel.org>,
"<kvm@vger.kernel.org>" <kvm@vger.kernel.org>
Subject: Re: [PATCH 0/8] kvm/ppc: fixes for 3.10
Date: Wed, 10 Jul 2013 06:03:44 +0000 [thread overview]
Message-ID: <51DCF940.7050601@windriver.com> (raw)
In-Reply-To: <3EC1C058-1CAE-4A5E-AEEE-2D9023EEE95D@suse.de>
On 07/10/2013 05:33 AM, Alexander Graf wrote:
>
> On 09.07.2013, at 11:09, tiejun.chen wrote:
>
>> On 07/09/2013 04:53 PM, Alexander Graf wrote:
>>>
>>>
>>> Am 09.07.2013 um 09:21 schrieb "tiejun.chen" <tiejun.chen@windriver.com>:
>>>
>>>> On 06/07/2013 08:16 AM, Scott Wood wrote:
>>>>> Most of these have been posted before, but I grouped them together as
>>>>> there are some contextual dependencies between them.
>>>>>
>>>>> Gleb/Paolo: As Alex doesn't appear to be back yet, can you apply these
>>>>> if there's no objection over the next few days?
>>>>
>>>> Scott and Alex,
>>>>
>>>> Any plan to merge these commits into git://github.com/agraf/linux-2.6.git as well?
>>>
>>> Which commits exactly are you missing there?
>>
>> Alex,
>>
>> Four patches,
>>
>> kvm/ppc/booke: Delay kvmppc_lazy_ee_enable
>> kvm/ppc/booke64: Fix lazy ee handling in kvmppc_handle_exit()
>> kvm/ppc/booke: Hold srcu lock when calling gfn functions
>> kvm/ppc/booke64: Disable e6500 support
>>
>> are already in Linus's tree,
>>
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?qt=author&q=Scott+Wood
>>
>> So should we sync these commits into your tree?
>
> They should already be in there?
Yes, I already see this.
Thanks,
Tiejun
prev parent reply other threads:[~2013-07-10 6:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 0:16 [PATCH 0/8] kvm/ppc: fixes for 3.10 Scott Wood
2013-06-07 0:16 ` [PATCH 1/8] kvm/ppc/booke64: Fix AltiVec interrupt numbers and build breakage Scott Wood
2013-06-07 0:16 ` [PATCH 2/8] kvm/ppc/booke64: Disable e6500 support Scott Wood
2013-06-07 0:16 ` [PATCH 3/8] kvm/ppc/booke: Hold srcu lock when calling gfn functions Scott Wood
2013-06-07 0:16 ` [PATCH 4/8] kvm/ppc/booke64: Fix lazy ee handling in kvmppc_handle_exit() Scott Wood
2013-06-07 0:16 ` [PATCH 5/8] kvm/ppc: Call trace_hardirqs_on before entry Scott Wood
2013-06-07 0:16 ` [PATCH 6/8] kvm/ppc: IRQ disabling cleanup Scott Wood
2013-06-07 0:16 ` [PATCH 7/8] kvm/ppc/booke: Delay kvmppc_fix_ee_before_entry Scott Wood
2013-06-07 0:16 ` [PATCH 8/8] kvm/ppc/booke: Don't call kvm_guest_enter twice Scott Wood
2013-06-09 8:09 ` [PATCH 0/8] kvm/ppc: fixes for 3.10 Gleb Natapov
2013-06-10 19:52 ` Scott Wood
2013-06-17 15:27 ` Paolo Bonzini
2013-07-09 7:21 ` tiejun.chen
2013-07-09 8:53 ` Alexander Graf
2013-07-09 9:09 ` tiejun.chen
2013-07-09 21:33 ` Alexander Graf
2013-07-10 6:03 ` tiejun.chen [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=51DCF940.7050601@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=agraf@suse.de \
--cc=gleb@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mihai.caraman@freescale.com \
--cc=pbonzini@redhat.com \
--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