linux-kernel - Re: [PATCH 13/13] memblock, x86: Replace memblock_x86_reserve/free

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 14 Jul 2011 22:41:59 +0200
From:	Tejun Heo <tj@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	mingo@...hat.com, tglx@...utronix.de, benh@...nel.crashing.org,
	yinghai@...nel.org, davem@...emloft.net,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	x86@...nel.org
Subject: Re: [PATCH 13/13] memblock, x86: Replace memblock_x86_reserve/free_range()
 with generic ones

Hello,

On Thu, Jul 14, 2011 at 10:38 PM, H. Peter Anvin <hpa@...or.com> 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. :(

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/