All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	rkrcmar@redhat.com, kvm@vger.kernel.org,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [GIT PULL] Last straggler for 4.20-rc8 or final
Date: Fri, 21 Dec 2018 23:40:40 +0100	[thread overview]
Message-ID: <20181221224040.GA25147@zn.tnic> (raw)
In-Reply-To: <1545397742-48818-1-git-send-email-pbonzini@redhat.com>

+ mingo.

On Fri, Dec 21, 2018 at 02:09:02PM +0100, Paolo Bonzini wrote:
> Linus,
> 
> The following changes since commit 7566ec393f4161572ba6f11ad5171fd5d59b0fbd:
> 
>   Linux 4.20-rc7 (2018-12-16 15:46:55 -0800)
> 
> are available in the git repository at:
> 
>   https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
> 
> for you to fetch changes up to 3cf85f9f6bd7b172122865432b4c6f0ec844e22a:
> 
>   KVM: x86: nSVM: fix switch to guest mmu (2018-12-19 22:19:22 +0100)
> 
> A simple patch for a pretty bad bug.  I haven't yet sent my 4.21 pull
> request because currently I'm waiting for a patch to be removed from
> tip (MPX removal breaks KVM live migration and was committed without
> Cc or Ack from me) and until that happens I cannot finalize my
> conflict resolution instructions.

Lemme make sure I understand it correctly: you'd like us to not send

https://git.kernel.org/tip/eb012ef3b4e331ae479dd7cd9378041d9b7f851c

up now and delay it for 4.22, right?

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

  parent reply	other threads:[~2018-12-21 22:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21 13:09 [GIT PULL] Last straggler for 4.20-rc8 or final Paolo Bonzini
2018-12-21 19:30 ` pr-tracker-bot
2018-12-21 22:40 ` Borislav Petkov [this message]
2018-12-22  7:47   ` Paolo Bonzini
2018-12-22 11:44     ` Borislav Petkov
2018-12-22 20:59     ` Ingo Molnar
2018-12-23  8:45       ` 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=20181221224040.GA25147@zn.tnic \
    --to=bp@alien8.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=torvalds@linux-foundation.org \
    /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.