All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Andre Przywara <Andre.Przywara@arm.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
	"svaidy@linux.vnet.ibm.com" <svaidy@linux.vnet.ibm.com>,
	"matt@ozlabs.org" <matt@ozlabs.org>
Subject: Re: [PATCH 1/2] powerpc: Define the hcall opcodes & return values we need
Date: Fri, 19 Jun 2015 10:35:03 +0000	[thread overview]
Message-ID: <20150619103502.GD18017@arm.com> (raw)
In-Reply-To: <1434698461-15539-1-git-send-email-mpe@ellerman.id.au>

On Fri, Jun 19, 2015 at 08:21:00AM +0100, Michael Ellerman wrote:
> Now that we don't have the kernel header on hand, just define the
> minimum set of hcall opcodes and return values we need in order to
> build.

Thanks Michael!

I pushed both of these out.

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Andre Przywara <Andre.Przywara@arm.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
	"svaidy@linux.vnet.ibm.com" <svaidy@linux.vnet.ibm.com>,
	"matt@ozlabs.org" <matt@ozlabs.org>
Subject: Re: [PATCH 1/2] powerpc: Define the hcall opcodes & return values we need
Date: Fri, 19 Jun 2015 11:35:03 +0100	[thread overview]
Message-ID: <20150619103502.GD18017@arm.com> (raw)
In-Reply-To: <1434698461-15539-1-git-send-email-mpe@ellerman.id.au>

On Fri, Jun 19, 2015 at 08:21:00AM +0100, Michael Ellerman wrote:
> Now that we don't have the kernel header on hand, just define the
> minimum set of hcall opcodes and return values we need in order to
> build.

Thanks Michael!

I pushed both of these out.

Will

  parent reply	other threads:[~2015-06-19 10:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19  7:21 [PATCH 1/2] powerpc: Define the hcall opcodes & return values we need Michael Ellerman
2015-06-19  7:21 ` Michael Ellerman
2015-06-19  7:21 ` [PATCH 2/2] powerpc: Enable 32-bit build Michael Ellerman
2015-06-19  7:21   ` Michael Ellerman
2015-06-19  7:40 ` [PATCH 1/2] powerpc: Define the hcall opcodes & return values we need Michael Ellerman
2015-06-19  7:40   ` Michael Ellerman
2015-06-19 10:35 ` Will Deacon [this message]
2015-06-19 10:35   ` Will Deacon
2015-06-23  9:33 ` Paolo Bonzini
2015-06-23  9:33   ` Paolo Bonzini
2015-06-23 10:05   ` Michael Ellerman
2015-06-23 10:05     ` Michael Ellerman
2015-06-23 10:31     ` Andre Przywara
2015-06-23 10:31       ` Andre Przywara
2015-06-23 10:33       ` Paolo Bonzini
2015-06-23 10:33         ` Paolo Bonzini

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=20150619103502.GD18017@arm.com \
    --to=will.deacon@arm.com \
    --cc=Andre.Przywara@arm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=matt@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=svaidy@linux.vnet.ibm.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.