All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [GIT PULL] Please pull my kvm-ppc-fixes-5.3-1 tag
Date: Tue, 27 Aug 2019 17:49:37 +0200	[thread overview]
Message-ID: <20190827154937.GA65641@flask> (raw)
In-Reply-To: <20190827095338.GA22875@blackberry>

2019-08-27 19:53+1000, Paul Mackerras:
> Paolo or Radim,
> 
> Please do a pull from my kvm-ppc-fixes-5.3-1 tag to get one small
> commit which I would like to go to Linus for 5.3 if possible, since it
> fixes a bug where a malicious guest could cause host CPUs to hang
> hard.  The fix is small and obviously correct.

Pulled, thanks.

WARNING: multiple messages have this Message-ID (diff)
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [GIT PULL] Please pull my kvm-ppc-fixes-5.3-1 tag
Date: Tue, 27 Aug 2019 15:49:37 +0000	[thread overview]
Message-ID: <20190827154937.GA65641@flask> (raw)
In-Reply-To: <20190827095338.GA22875@blackberry>

2019-08-27 19:53+1000, Paul Mackerras:
> Paolo or Radim,
> 
> Please do a pull from my kvm-ppc-fixes-5.3-1 tag to get one small
> commit which I would like to go to Linus for 5.3 if possible, since it
> fixes a bug where a malicious guest could cause host CPUs to hang
> hard.  The fix is small and obviously correct.

Pulled, thanks.

  reply	other threads:[~2019-08-27 15:49 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27  9:53 [GIT PULL] Please pull my kvm-ppc-fixes-5.3-1 tag Paul Mackerras
2019-08-27  9:53 ` Paul Mackerras
2019-08-27 15:49 ` Radim Krčmář [this message]
2019-08-27 15:49   ` Radim Krčmář
  -- strict thread matches above, loose matches on Subject: below --
2020-04-20 23:53 [GIT PULL] Please pull my kvm-ppc-fixes-5.7-1 tag Paul Mackerras
2020-04-20 23:53 ` Paul Mackerras
2020-04-21 13:37 ` Paolo Bonzini
2020-04-21 13:37   ` Paolo Bonzini
2019-12-19  0:19 [GIT PULL] Please pull my kvm-ppc-fixes-5.5-1 tag Paul Mackerras
2019-12-19  0:19 ` Paul Mackerras
2019-12-22 12:18 ` Paolo Bonzini
2019-12-22 12:18   ` Paolo Bonzini
2019-10-21  4:19 [GIT PULL] Please pull my kvm-ppc-fixes-5.4-1 tag Paul Mackerras
2019-10-21  4:19 ` Paul Mackerras
2019-10-22 11:12 ` Paolo Bonzini
2019-10-22 11:12   ` Paolo Bonzini
2019-05-30 11:59 [GIT PULL] Please pull my kvm-ppc-fixes-5.2-1 tag Paul Mackerras
2019-05-30 11:59 ` Paul Mackerras
2019-05-31 22:48 ` Paolo Bonzini
2019-05-31 22:48   ` Paolo Bonzini
2019-04-07 22:12 [GIT PULL] Please pull my kvm-ppc-fixes-5.1-1 tag Paul Mackerras
2019-04-07 22:12 ` Paul Mackerras
2019-04-18  4:05 ` Paul Mackerras
2019-04-18  4:05   ` Paul Mackerras
2019-04-18 16:53   ` Paolo Bonzini
2019-04-18 16:53     ` Paolo Bonzini
2018-03-03  9:17 [GIT PULL] Please pull my kvm-ppc-fixes-4.16-1 tag Paul Mackerras
2018-03-06 17:08 ` Radim Krčmář
2018-03-14  8:57 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.16-2 tag Paul Mackerras
2018-03-15 20:57 ` Paolo Bonzini
2018-03-23  4:46 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.16-3 tag Paul Mackerras
2018-03-23 17:21 ` Paolo Bonzini
2018-05-24  5:34 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.17-1 tag Paul Mackerras
2018-05-24 17:02 ` Radim Krčmář
2018-08-22 12:08 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.19-1 tag Paul Mackerras
2018-09-14  9:57 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.19-2 tag Paul Mackerras
2018-09-18 13:22 ` Paolo Bonzini
2018-10-05  0:29 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.19-3 tag Paul Mackerras
2018-10-05  7:43 ` Paolo Bonzini
2018-11-16 10:36 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.20-1 tag Paul Mackerras
2018-11-25 17:54 ` 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=20190827154937.GA65641@flask \
    --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.