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:	Wed, 11 Apr 2012 09:30:16 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: drop obsolete ARCH_BOOTMEM support

On Fri, Apr 06, 2012 at 02:47:35PM +0200, Sam Ravnborg wrote:
> From ae6cdc767f973f39cb205af4b80ff13f35a1b66e Mon Sep 17 00:00:00 2001
> From: Sam Ravnborg <sam@...nborg.org>
> Date: Fri, 6 Apr 2012 13:37:08 +0200
> Subject: [PATCH] x86: drop obsolete ARCH_BOOTMEM support
> 
> x86 unconditionally uses NO_BOOTMEM so there is no use
> of the HAVE_ARCH_BOOTMEM support as mm/bootmem.c is the
> only file referencing this symbol.
> 
> bootmem_arch_preferred_node() is the function referred
> in the mm/bootmem.c code and can thuis be dropped too.
> 
> x86 was the sole user of HAVE_ARCH_BOOTMEM - so there is
> an opportunity to clean up a little in mm/bootmem.c too
> if we do not expect other users to emerge.

avr32 seems to have it too?

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

Powered by blists - more mailing lists