linux-kernel - Re: [PATCH 1/6] arch/blackfin: Remove config HIGHMEM

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] [day] [month] [year] [list]

Date:	Sat, 7 Aug 2010 22:05:58 -0400
From:	Mike Frysinger <vapier.adi@...il.com>
To:	Christian Dietrich <qy03fugy@...d.informatik.uni-erlangen.de>
Cc:	Robin Getz <robin.getz@...log.com>, Tejun Heo <tj@...nel.org>,
	uclinux-dist-devel@...ckfin.uclinux.org,
	linux-kernel@...r.kernel.org,
	vamos-dev@...informatik.uni-erlangen.de
Subject: Re: [PATCH 1/6] arch/blackfin: Remove config HIGHMEM

On Mon, Aug 2, 2010 at 12:00, Christian Dietrich wrote:
> CONFIG_HIGHMEM can't be selected in blackfin, therefore all references
> to it can be removed from the arch/blackfin.

while currently we dont support highmem (as our current parts max out
at 512MiB), this should be feasible in the not-so-far future, in which
case we will have highmem support added.  so i'm inclined to leave it
be as in a highmem world, this is the code we'd want.  thanks though.
-mike
--
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/