public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-ppc@vger.kernel.org, KVM list <kvm@vger.kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PULL 0/4] ppc patch queue 2012-12-18
Date: Wed, 19 Dec 2012 11:40:15 +0200	[thread overview]
Message-ID: <20121219094015.GN11016@redhat.com> (raw)
In-Reply-To: <50D09B6D.4030203@suse.de>

On Tue, Dec 18, 2012 at 05:35:57PM +0100, Alexander Graf wrote:
> On 12/18/2012 04:20 PM, Gleb Natapov wrote:
> >On Tue, Dec 18, 2012 at 01:38:39PM +0100, Alexander Graf wrote:
> >>Hi Marcelo / Gleb,
> >>
> >>This is my current patch queue for ppc.  Please pull.
> >>
> >Is this for 3.8 or 3.9?
> 
> This is for 3.9, except for the UAPI one. That one should go into
> 3.8 and stable.
> 
It is good to have this information with pull request. Also patches for
3.8 go to master branch while patches for 3.9 go to next branch, so you
need to prepare separate pull requests for two of those.

> 
> Alex
> 
> >
> >>Changes include:
> >>
> >>   - important header fix for UAPI
> >>   - Book3S: PR: Enable fake sc 1 instruction for KVM on top of pHyp
> >>
> >>Alex
> >>
> >>
> >>The following changes since commit e11ae1a102b46f76441e328a2743ae5d6e201423:
> >>   Gleb Natapov (1):
> >>         KVM: remove unused variable.
> >>
> >>are available in the git repository at:
> >>
> >>   git://github.com/agraf/linux-2.6.git kvm-ppc-next
> >>
> >>Alexander Graf (2):
> >>       KVM: PPC: Only WARN on invalid emulation
> >>       KVM: PPC: Book3S: PR: Enable alternative instruction for SC 1
> >>
> >>Bharat Bhushan (1):
> >>       powerpc: Corrected include header path in kvm_para.h
> >>
> >>Mihai Caraman (1):
> >>       KVM: PPC: Fix SREGS documentation reference
> >>
> >>  Documentation/virtual/kvm/api.txt        |    2 +-
> >>  arch/powerpc/include/asm/kvm_ppc.h       |    1 +
> >>  arch/powerpc/include/uapi/asm/kvm_para.h |    2 +-
> >>  arch/powerpc/kvm/book3s_emulate.c        |   28 ++++++++++++++++++++++++++++
> >>  arch/powerpc/kvm/book3s_pr.c             |    5 +++++
> >>  arch/powerpc/kvm/powerpc.c               |    3 ++-
> >>  6 files changed, 38 insertions(+), 3 deletions(-)
> >--
> >			Gleb.

--
			Gleb.

      reply	other threads:[~2012-12-19  9:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18 12:38 [PULL 0/4] ppc patch queue 2012-12-18 Alexander Graf
2012-12-18 12:38 ` [PATCH 1/4] KVM: PPC: Fix SREGS documentation reference Alexander Graf
2012-12-18 12:38 ` [PATCH 2/4] KVM: PPC: Only WARN on invalid emulation Alexander Graf
2012-12-18 22:54   ` Scott Wood
2012-12-18 23:01     ` Alexander Graf
2012-12-18 23:05       ` Scott Wood
2012-12-18 23:09         ` Alexander Graf
2012-12-19  9:37       ` Gleb Natapov
2012-12-19  9:59         ` Alexander Graf
2012-12-19 10:00           ` Gleb Natapov
2012-12-18 12:38 ` [PATCH 3/4] KVM: PPC: Book3S: PR: Enable alternative instruction for SC 1 Alexander Graf
2012-12-18 12:38 ` [PATCH 4/4] powerpc: Corrected include header path in kvm_para.h Alexander Graf
2012-12-18 15:20 ` [PULL 0/4] ppc patch queue 2012-12-18 Gleb Natapov
2012-12-18 16:35   ` Alexander Graf
2012-12-19  9:40     ` Gleb Natapov [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=20121219094015.GN11016@redhat.com \
    --to=gleb@redhat.com \
    --cc=agraf@suse.de \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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