From: Will Deacon <will.deacon@arm.com>
To: Balbir Singh <bsingharora@gmail.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
kvm@vger.kernel.org, Michael Neuling <mikey@neuling.org>
Subject: Re: [PATCH 2/5] Add basic infrastructure to run tasks on vCPUs
Date: Fri, 1 Apr 2016 13:27:01 +0100 [thread overview]
Message-ID: <20160401122659.GD3604@arm.com> (raw)
In-Reply-To: <CAKTCnzki=-mc0EH3+4ti+8e7Xfz7jmoLjvsZVNUnoay7v0Evqg@mail.gmail.com>
On Fri, Apr 01, 2016 at 10:29:27PM +1100, Balbir Singh wrote:
> Agreed
>
> Will should I resend this bit with a new From?
Sure, feel free to repost the whole series with Michael's acks too.
Will
next prev parent reply other threads:[~2016-04-01 12:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 11:28 [PATCH 0/5] Add support for ppc64le in kvmtool Balbir Singh
2016-03-31 11:28 ` [PATCH 1/5] Add basic little endian support Balbir Singh
2016-03-31 11:28 ` [PATCH 2/5] Add basic infrastructure to run tasks on vCPUs Balbir Singh
2016-04-01 10:42 ` Michael Ellerman
2016-04-01 11:29 ` Balbir Singh
2016-04-01 12:27 ` Will Deacon [this message]
2016-04-07 1:12 ` Balbir Singh
2016-03-31 11:28 ` [PATCH 3/5] Implement H_SET_MODE for ppc64le Balbir Singh
2016-03-31 11:28 ` [PATCH 4/5] Fix a race during exit processing Balbir Singh
2016-04-11 15:37 ` Will Deacon
2016-03-31 11:28 ` [PATCH 5/5] Implement spapr pci for little endian systems Balbir Singh
2016-03-31 13:38 ` [PATCH 0/5] Add support for ppc64le in kvmtool Laurent Vivier
2016-03-31 13:38 ` Laurent Vivier
2016-04-01 0:12 ` Balbir Singh
2016-04-01 0:12 ` Balbir Singh
2016-04-04 8:34 ` Balbir Singh
2016-04-04 8:34 ` Balbir Singh
2016-04-04 8:41 ` Laurent Vivier
2016-04-04 8:41 ` Laurent Vivier
2016-04-04 10:24 ` Balbir Singh
2016-04-04 10:24 ` Balbir Singh
2016-04-04 12:21 ` Laurent Vivier
2016-04-04 12:21 ` Laurent Vivier
2016-04-01 10:47 ` Michael Ellerman
2016-04-01 10:48 ` Will Deacon
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=20160401122659.GD3604@arm.com \
--to=will.deacon@arm.com \
--cc=bsingharora@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
/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.