linux-kernel - Re: [PATCH 2/3]: xvmalloc memory allocator

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]

Message-ID: <84144f020903182308r1082e418k7deb441774af4d89@mail.gmail.com>
Date:	Wed, 18 Mar 2009 23:08:27 -0700
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Nitin Gupta <ngupta@...are.org>
Cc:	Christoph Lameter <cl@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3]: xvmalloc memory allocator

On 3/18/09, Nitin Gupta <ngupta@...are.org> wrote:
> I can see quite some places for cleanups (like macros for
> reaching next free block etc). Do you think CamelCase will be acceptable
> for now? and also keeping xvmalloc name? Other than these, I will
> check for potential cleanups and send updated diffs.

No, I do not think it is acceptable for core kernel code.
--
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/