From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH 13/13] memblock, x86: Replace memblock_x86_reserve/free_range() with generic ones Date: Thu, 14 Jul 2011 13:43:38 -0700 Message-ID: <4E1F54FA.1060506@zytor.com> References: <1310462166-31469-1-git-send-email-tj@kernel.org> <1310462166-31469-14-git-send-email-tj@kernel.org> <4E1F4D2C.3000507@zytor.com> <4E1F5040.50004@zytor.com> <4E1F53D9.2000606@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from terminus.zytor.com ([198.137.202.10]:39358 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754211Ab1GNUnx (ORCPT ); Thu, 14 Jul 2011 16:43:53 -0400 In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-ID: To: Tejun Heo Cc: mingo@redhat.com, tglx@linutronix.de, benh@kernel.crashing.org, yinghai@kernel.org, davem@davemloft.net, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, x86@kernel.org On 07/14/2011 01:41 PM, Tejun Heo wrote: > Hello, > > On Thu, Jul 14, 2011 at 10:38 PM, H. Peter Anvin wrote: >>> Hmm... I was only looking at the early boot messages which didn't >>> include the io ranges. It ultimately is a cosmetic issue so my >>> opinions aren't very strong but I think we can leave [mm]io ranges >>> alone and converge the rest into [ ) ranges sans the brackets? >> >> Agreed it's a cosmetic issue... this discussion has already been had, >> though, and the consensus is to move the kernel to the standardized >> resource format. > > OIC, in that case, please go ahead and change it. It seems that we > haven't been too successful at applying the decision tho. :( > It's a work in progress. -hpa