From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: 2.6.32.12: Build warning due to 78ce64a384 / missing in 2.6.33? Date: Tue, 27 Apr 2010 10:46:09 +0300 Message-ID: <20100427074609.GB10044@redhat.com> References: <4BD5D34E.4080503@web.de> <20100427061733.GA10044@redhat.com> <4BD69521.8080204@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jan Kiszka , kvm , Marcelo Tosatti To: Avi Kivity Return-path: Received: from mx1.redhat.com ([209.132.183.28]:62432 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752758Ab0D0HqM (ORCPT ); Tue, 27 Apr 2010 03:46:12 -0400 Content-Disposition: inline In-Reply-To: <4BD69521.8080204@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Apr 27, 2010 at 10:41:21AM +0300, Avi Kivity wrote: > On 04/27/2010 09:17 AM, Gleb Natapov wrote: > > > >>The fact that 2.6.33.3 does not generate this makes me wonder why it > >>obviously lacks the above patch. Not required or not yet queued? > >> > >Doesn't make much sense to include it in stable-32, but not stable-33. I > >think stable-32 just has more attention since it is used by many > >distribution as base kernel. > > This was due to the previous process of mindlessly applying patches > to stable without testing/looking at them first. Hopefully the new > process will deliver better results. > > Gleb, can you look at 2.6.33 and see if it is missing something, or > maybe the warning is gone for another reason? > Already looked at it. 2.6.33-stable misses the patch that cause warning in 2.6.32-stable. -- Gleb.