From mboxrd@z Thu Jan 1 00:00:00 1970 From: Radim =?utf-8?B?S3LEjW3DocWZ?= Subject: Re: [GIT PULL] Please pull my kvm-ppc-next-4.16-2 tag Date: Sat, 10 Feb 2018 15:52:32 +0100 Message-ID: <20180210145231.GA4148@flask> References: <20180209094145.GB7725@fergus.ozlabs.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Paolo Bonzini , kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, David Gibson To: Paul Mackerras Return-path: Received: from mx3-rdu2.redhat.com ([66.187.233.73]:53488 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750835AbeBJOwx (ORCPT ); Sat, 10 Feb 2018 09:52:53 -0500 Content-Disposition: inline In-Reply-To: <20180209094145.GB7725@fergus.ozlabs.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: 2018-02-09 20:41+1100, Paul Mackerras: > Paolo or Radim, > > Please do a pull from my kvm-ppc-next-4.16-2 tag to get some PPC KVM > fixes that I would like to have go into 4.16. Most of them are quite > self-contained; there are two that are larger (and arguably don't > quite count as bug fixes), but I have checked them carefully and > convinced myself that they have a low risk of causing regressions, and > they do address issues that have been found in testing, so I put them > in. > > With things like this I would normally put them in my kvm-ppc-fixes > branch and base it on current upstream. However, as far as I can see > the kvm next branch hasn't been merged upstream yet. Therefore I made > this series a continuation of my kvm-ppc-next branch. I have resolved the resulting conflict and pulled, thanks. > When do you expect that kvm/next will get merged upstream? Hopefully on Sunday, sorry for the delay.