From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM: x86: disable kvmclock on non constant TSC hosts Date: Thu, 12 Feb 2009 18:35:13 +0200 Message-ID: <49944FC1.8020208@redhat.com> References: <20090210172407.GA31394@amt.cnet> <20090210225945.GA5373@amt.cnet> <4992BE30.6030009@redhat.com> <1234382903.14052.246.camel@blaa> <20090211225543.GA15230@amt.cnet> <4993F3AA.9080800@redhat.com> <20090212162914.GA22597@x200.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , Mark McLoughlin , Glauber de Oliveira Costa , kvm-devel To: Chris Wright Return-path: Received: from mx2.redhat.com ([66.187.237.31]:55514 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751107AbZBLQfQ (ORCPT ); Thu, 12 Feb 2009 11:35:16 -0500 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n1CGZGht024276 for ; Thu, 12 Feb 2009 11:35:16 -0500 In-Reply-To: <20090212162914.GA22597@x200.localdomain> Sender: kvm-owner@vger.kernel.org List-ID: Chris Wright wrote: > * Avi Kivity (avi@redhat.com) wrote: > >> Does 'Cc: stable' mean -stable picks it up automatically? That doesn't >> seem right. >> > > Yes. If you add "Cc: stable@kernel.org" to the commit message, it will > get routed to stable when it's committed upstream (still gets human > touch, it's not automatically committed to stable). > What about porting the patch? And testing it? -- error compiling committee.c: too many arguments to function