Date: Mon, 13 Dec 2010 10:45:59 +0100
From: Andi Kleen <andi@firstfloor.org>
To: Avi Kivity <avi@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>, mst@redhat.com, gregkh@suse.de,
        ak@linux.intel.com, linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] [104/223] KVM: Write protect memory after slot swap
Message-ID: <20101213094559.GD999@basil.fritz.box>
References: <201012131244.547034648@firstfloor.org>
 <20101212234644.B05DAB27BF@basil.firstfloor.org>
 <4D05DC98.40105@redhat.com>
 <044a861a2279c7e3e328c73e6694fbf3.squirrel@www.firstfloor.org>
 <4D05E096.6060307@redhat.com>
 <74ff92a8c4cf72e42e7559de72e77b52.squirrel@www.firstfloor.org>
 <4D05E2A5.8070204@redhat.com>
 <20101213091254.GA999@basil.fritz.box>
 <4D05E483.1000106@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D05E483.1000106@redhat.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 846
Lines: 23

> >Do you want to do the autotest explicitely for .35 too and no automatic
> >backports and do the same procedure as for newer kernels?
> >
> >I can do that, but you would need to do it for a long time.
> 
> Yes.  In fact it gets more important as time goes by, since as time
> goes by patches are more likely to cause regressions due to changes
> in the code base.

Ok. But this requires that you do this regularly for .35 too.
If you do that that's great. 

I will not automatically backport KVM patches anymore,
but wait/ping you instead.

-Andi
-- 
ak@linux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/