Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755930Ab2KZUKF (ORCPT <rfc822;w@1wt.eu>);
	Mon, 26 Nov 2012 15:10:05 -0500
Received: from mga09.intel.com ([134.134.136.24]:59701 "EHLO mga09.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1755547Ab2KZUKE (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 26 Nov 2012 15:10:04 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.83,323,1352102400"; 
   d="scan'208";a="224601330"
Message-ID: <50B3CC90.8090800@linux.intel.com>
Date: Mon, 26 Nov 2012 12:09:52 -0800
From: "H. Peter Anvin" <hpa@linux.intel.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Herton Ronaldo Krzesinski <herton.krzesinski@canonical.com>
CC: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
        kernel-team@lists.ubuntu.com, Jacob Shin <jacob.shin@amd.com>
Subject: Re: [PATCH 168/270] x86: Exclude E820_RESERVED regions and memory
 holes above 4 GB from direct mapping.
References: <1353949160-26803-1-git-send-email-herton.krzesinski@canonical.com> <1353949160-26803-169-git-send-email-herton.krzesinski@canonical.com> <50B3AEA1.9010802@linux.intel.com> <20121126200819.GD3331@herton-Z68MA-D2H-B3>
In-Reply-To: <20121126200819.GD3331@herton-Z68MA-D2H-B3>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1057
Lines: 25

On 11/26/2012 12:08 PM, Herton Ronaldo Krzesinski wrote:
> On Mon, Nov 26, 2012 at 10:02:09AM -0800, H. Peter Anvin wrote:
>> On 11/26/2012 08:57 AM, Herton Ronaldo Krzesinski wrote:
>>> 3.5.7u1 -stable review patch.  If anyone has any objections, please let me know.
>>
>> What kind of version number is that?
> 
> This is an "extended stable" tree, a fork from the last 3.5 stable
> update (3.5 isn't maintained anymore by stable upstream). Thus
> it seemed better to just follow last released 3.5 stable version, and
> append an extraversion to it, which I chose in the end to be u<n>
> (u == update). It's unlikely that other 3.5 stable upstream update will
> be done, in any case I expect this way to avoid any issue.
> 

Why not 3.5.7.1 sticking with the pre-established version numbering scheme?

	-hpa


--
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/