From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: 2.6.32.12: Build warning due to 78ce64a384 / missing in 2.6.33? Date: Tue, 27 Apr 2010 10:41:21 +0300 Message-ID: <4BD69521.8080204@redhat.com> References: <4BD5D34E.4080503@web.de> <20100427061733.GA10044@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , kvm , Marcelo Tosatti To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:49899 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752418Ab0D0Hl0 (ORCPT ); Tue, 27 Apr 2010 03:41:26 -0400 In-Reply-To: <20100427061733.GA10044@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.