From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/4] KVM updates for Linux 3.1.8 Date: Thu, 12 Jan 2012 18:25:43 +0200 Message-ID: <4F0F0987.3030500@redhat.com> References: <1326364794-18150-1-git-send-email-avi@redhat.com> <20120112161510.GA11287@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: stable@vger.kernel.org, kvm@vger.kernel.org, Marcelo Tosatti To: Greg KH Return-path: Received: from mx1.redhat.com ([209.132.183.28]:22680 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751938Ab2ALQZt (ORCPT ); Thu, 12 Jan 2012 11:25:49 -0500 In-Reply-To: <20120112161510.GA11287@kroah.com> Sender: kvm-owner@vger.kernel.org List-ID: On 01/12/2012 06:15 PM, Greg KH wrote: > On Thu, Jan 12, 2012 at 12:39:50PM +0200, Avi Kivity wrote: > > The following patches want to be applied to the 3.1 branch. "All users must > > update". > > Do any of these also need to go to the 3.0 branch? Yes. But for kvm we regression test stable patches, and I haven't done this yet. I find the normal stable process, while very convenient, frightening. -- error compiling committee.c: too many arguments to function