All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Paul Mackerras <paulus@ozlabs.org>,
	kvm@vger.kernel.org, David Gibson <david@gibson.dropbear.id.au>,
	kvm-ppc@vger.kernel.org
Subject: Re: [GIT PULL] Please pull my kvm-ppc-fixes branch
Date: Tue, 20 Jun 2017 17:17:01 +0200	[thread overview]
Message-ID: <20170620151700.GF10325@potion> (raw)
In-Reply-To: <3bc0aeed-136b-5b7f-03a4-17b3aae31842@redhat.com>

2017-06-20 14:55+0200, Paolo Bonzini:
> On 20/06/2017 14:39, Radim Krčmář wrote:
> > 2017-06-20 14:30+1000, Paul Mackerras:
> >> Paolo,
> >>
> >> Please do a pull from my kvm-ppc-fixes branch to get 6 commits that I
> >> would like to have go into 4.12, because they fix problems that could
> >> cause hangs or crashes in the host (the first and last commit, but
> >> only on POWER9 systems), or they fix problems that could allow guests
> >> to potentially affect or disrupt the execution of the controlling
> >> userspace (the other four).  They are all marked to go to stable.
> > 
> > Pulled, but only locally at the moment -- would you like me to apply
> > "[PATCH v2] KVM: MIPS: Fix maybe-uninitialized build failure" directly?
> 
> Why not, isn't the tree yours? :)

Right, and the arch doesn't even match ... let's forget I asked. :)

Pushed into kvm/master, thanks.

WARNING: multiple messages have this Message-ID (diff)
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Paul Mackerras <paulus@ozlabs.org>,
	kvm@vger.kernel.org, David Gibson <david@gibson.dropbear.id.au>,
	kvm-ppc@vger.kernel.org
Subject: Re: [GIT PULL] Please pull my kvm-ppc-fixes branch
Date: Tue, 20 Jun 2017 15:17:01 +0000	[thread overview]
Message-ID: <20170620151700.GF10325@potion> (raw)
In-Reply-To: <3bc0aeed-136b-5b7f-03a4-17b3aae31842@redhat.com>

2017-06-20 14:55+0200, Paolo Bonzini:
> On 20/06/2017 14:39, Radim Krčmář wrote:
> > 2017-06-20 14:30+1000, Paul Mackerras:
> >> Paolo,
> >>
> >> Please do a pull from my kvm-ppc-fixes branch to get 6 commits that I
> >> would like to have go into 4.12, because they fix problems that could
> >> cause hangs or crashes in the host (the first and last commit, but
> >> only on POWER9 systems), or they fix problems that could allow guests
> >> to potentially affect or disrupt the execution of the controlling
> >> userspace (the other four).  They are all marked to go to stable.
> > 
> > Pulled, but only locally at the moment -- would you like me to apply
> > "[PATCH v2] KVM: MIPS: Fix maybe-uninitialized build failure" directly?
> 
> Why not, isn't the tree yours? :)

Right, and the arch doesn't even match ... let's forget I asked. :)

Pushed into kvm/master, thanks.

  reply	other threads:[~2017-06-20 15:17 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20  4:30 [GIT PULL] Please pull my kvm-ppc-fixes branch Paul Mackerras
2017-06-20  4:30 ` Paul Mackerras
2017-06-20 12:39 ` Radim Krčmář
2017-06-20 12:39   ` Radim Krčmář
2017-06-20 12:55   ` Paolo Bonzini
2017-06-20 12:55     ` Paolo Bonzini
2017-06-20 15:17     ` Radim Krčmář [this message]
2017-06-20 15:17       ` Radim Krčmář
2017-06-20 23:37       ` Paul Mackerras
2017-06-20 23:37         ` Paul Mackerras
2017-06-21 10:30         ` Paolo Bonzini
2017-06-21 10:30           ` Paolo Bonzini
  -- strict thread matches above, loose matches on Subject: below --
2017-10-19  4:20 Paul Mackerras
2017-10-19  4:20 ` Paul Mackerras
2017-10-19 13:11 ` Radim Krčmář
2017-10-19 13:11   ` Radim Krčmář
2017-09-14  4:06 Paul Mackerras
2017-09-14  4:06 ` Paul Mackerras
2017-08-30  6:21 Paul Mackerras
2017-08-30  6:21 ` Paul Mackerras
2017-09-08 14:37 ` Radim Krčmář
2017-09-08 14:37   ` Radim Krčmář
2017-09-09 13:38   ` Paolo Bonzini
2017-09-09 13:38     ` Paolo Bonzini
2017-09-12  4:01     ` Paul Mackerras
2017-09-12  4:01       ` Paul Mackerras
2017-08-25  1:38 Paul Mackerras
2017-08-25  1:38 ` Paul Mackerras
2017-08-25  7:02 ` Paolo Bonzini
2017-08-25  7:02   ` Paolo Bonzini
2017-08-25  9:06   ` Paul Mackerras
2017-08-25  9:06     ` Paul Mackerras
2017-07-26  4:43 Paul Mackerras
2017-07-26  4:43 ` Paul Mackerras
2017-07-01 10:11 [GIT PULL] Please pull my kvm-ppc-fixes branch again Paul Mackerras
2017-07-01 10:11 ` Paul Mackerras
2017-07-03  8:40 ` Paolo Bonzini
2017-07-03  8:40   ` Paolo Bonzini
2017-07-05  6:54   ` Paul Mackerras
2017-07-05  6:54     ` Paul Mackerras
2017-05-15  8:16 [GIT PULL] Please pull my kvm-ppc-fixes branch Paul Mackerras
2017-05-15  8:16 ` Paul Mackerras
2017-05-15  8:32 ` Christian Zigotzky
2017-05-15  8:32   ` Christian Zigotzky
2017-05-16 13:52 ` Radim Krčmář
2017-05-16 13:52   ` Radim Krčmář
2017-04-06  6:28 Paul Mackerras
2017-04-06  6:28 ` Paul Mackerras
2017-04-06 14:37 ` Radim Krčmář
2017-04-06 14:37   ` Radim Krčmář
2017-03-02  1:55 Paul Mackerras
2017-03-02  1:55 ` Paul Mackerras
2017-03-02 11:00 ` Paolo Bonzini
2017-03-02 11:00   ` Paolo Bonzini
2017-03-02 21:04 ` Radim Krčmář
2017-03-02 21:04   ` Radim Krčmář
2016-03-08 10:54 Paul Mackerras
2016-03-08 10:54 ` Paul Mackerras
2015-12-10  3:12 Paul Mackerras
2015-12-10  3:12 ` Paul Mackerras
2015-12-11 11:30 ` Paolo Bonzini
2015-12-11 11:30   ` Paolo Bonzini
2015-11-12  5:35 Paul Mackerras
2015-11-12  5:35 ` Paul Mackerras
2015-11-12  9:11 ` Paolo Bonzini
2015-11-12  9:11   ` 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=20170620151700.GF10325@potion \
    --to=rkrcmar@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=paulus@ozlabs.org \
    --cc=pbonzini@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 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.