From: Alexander Graf <agraf@suse.de>
To: Michael Neuling <mikey@neuling.org>
Cc: Bharat Bhushan <r65777@freescale.com>,
linuxppc-dev@lists.ozlabs.org, benh@kernel.crashing.org,
linux-kernel@vger.kernel.org, scottwood@freescale.com,
Bharat Bhushan <bharat.bhushan@freescale.com>
Subject: Re: [PATCH 0/2] powerpc: allow kvm to use kerel debug framework
Date: Fri, 4 Oct 2013 16:40:55 +0200 [thread overview]
Message-ID: <A0DA1F6E-02F2-4CFC-B4B4-2D545E96DF32@suse.de> (raw)
In-Reply-To: <21895.1373441122@ale.ozlabs.ibm.com>
On 10.07.2013, at 09:25, Michael Neuling wrote:
> Alexander Graf <agraf@suse.de> wrote:
>
>>
>> On 09.07.2013, at 06:24, Michael Neuling wrote:
>>
>>> Alexander Graf <agraf@suse.de> wrote:
>>>
>>>>
>>>> On 04.07.2013, at 08:15, Bharat Bhushan wrote:
>>>>
>>>>> From: Bharat Bhushan <bharat.bhushan@freescale.com>
>>>>>
>>>>> This patchset moves the debug registers in a structure, which allows
>>>>> kvm to use same structure for debug emulation.
>>>>>
>>>>> Note: Earilier a patchset "https://lists.ozlabs.org/pipermail/linuxppc-dev/2013-June/108132.html"
>>>>> was sent which is a bunch of six patches. That patchset is divided into two parts:
>>>>> 1) powerpc specific changes (These 2 patches are actually have those changes)
>>>>> 2) KVM specific changes (will send separate patch on agraf repository)
>>>>
>>>> Mikey, if you like those could you please apply the into a topic
>>>> branch and get that one merged with Ben? I'd also pull it into my tree
>>>> then.
>>>
>>> benh would pull these directly.
>>>
>>> I'll have a chat with him to see if he wants my ACK before he does that.
>>
>> I have a bunch of patches that I need to apply on top, so I need a topic branch.
>
> I've acked the PPC specific bits of the v6 version of these patches.
>
> benh said he'll open a topic branch for you sometime next week and he'll
> stick them in there.
After talking to Ben about it, I've just put these into kvm-ppc-queue, so they will hit Linus' tree through the kvm tree.
Alex
prev parent reply other threads:[~2013-10-04 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 6:15 Bharat Bhushan
2013-07-04 6:15 ` [PATCH 1/2] powerpc: remove unnecessary line continuations Bharat Bhushan
2013-07-10 7:25 ` Michael Neuling
2013-07-04 6:15 ` [PATCH 2/2] powerpc: move debug registers in a structure Bharat Bhushan
2013-07-10 7:25 ` Michael Neuling
2013-07-09 1:00 ` [PATCH 0/2] powerpc: allow kvm to use kerel debug framework Alexander Graf
2013-07-09 4:24 ` Michael Neuling
2013-07-09 21:54 ` Alexander Graf
2013-07-10 7:25 ` Michael Neuling
2013-07-10 7:50 ` Alexander Graf
2013-07-25 10:17 ` Alexander Graf
2013-09-12 14:29 ` Alexander Graf
2013-10-04 14:40 ` Alexander Graf [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=A0DA1F6E-02F2-4CFC-B4B4-2D545E96DF32@suse.de \
--to=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=bharat.bhushan@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=r65777@freescale.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
all inboxes | Powered by JetHome®