All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jinpu Wang <jinpu.wang@profitbricks.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable <stable@vger.kernel.org>
Subject: Re: [stable-4.14 0/2] 2 kvm fix for 4.14
Date: Thu, 8 Mar 2018 09:43:45 +0100	[thread overview]
Message-ID: <CAMGffEm1XK0hY8qn8Ym9CdKHV00S1M6PmULbFOwJLDPBU184ZA@mail.gmail.com> (raw)
In-Reply-To: <20180307171713.GA7097@kroah.com>

On Wed, Mar 7, 2018 at 6:17 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Wed, Mar 07, 2018 at 05:04:03PM +0100, Jack Wang wrote:
>> From: Jack Wang <jinpu.wang@profitbricks.com>
>>
>> Hi Greg,
>>
>> I noticed 2 fixes for kvm are missing in your queue-4.14, both are bugfix,
>> can be cherry pick cleanly.
>>
>> The patch from Tianyu should close bug below, also included in 3.16
>> https://bugzilla.kernel.org/show_bug.cgi?id=198991
>
> Thanks for these, now queued up.
>
> greg k-h

Thanks Greg.

-- 
Jack Wang
Linux Kernel Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Tel:       +49 30 577 008  042
Fax:      +49 30 577 008 299
Email:    jinpu.wang@profitbricks.com
URL:      https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss,  Matthias Steinberg

      reply	other threads:[~2018-03-08  8:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 16:04 [stable-4.14 0/2] 2 kvm fix for 4.14 Jack Wang
2018-03-07 16:04 ` [stable-4.14 1/2] KVM/x86: Fix wrong macro references of X86_CR0_PG_BIT and X86_CR4_PAE_BIT in kvm_valid_sregs() Jack Wang
2018-03-07 16:04 ` [stable-4.14 2/2] KVM/x86: remove WARN_ON() for when vm_munmap() fails Jack Wang
2018-03-07 17:17 ` [stable-4.14 0/2] 2 kvm fix for 4.14 Greg KH
2018-03-08  8:43   ` Jinpu Wang [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=CAMGffEm1XK0hY8qn8Ym9CdKHV00S1M6PmULbFOwJLDPBU184ZA@mail.gmail.com \
    --to=jinpu.wang@profitbricks.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.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.