linux-kernel - Re: 2.6.31 -mm merge plans

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20090610190841.GT8633@ZenIV.linux.org.uk>
Date:	Wed, 10 Jun 2009 20:08:41 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.31 -mm merge plans

On Wed, Jun 10, 2009 at 11:51:40AM -0700, Andrew Morton wrote:

> proc-merge-arrayc-into-basec.patch
> proc-merge-arrayc-into-basec-checkpatch-fixes.patch

I'm not sure that there's any point in that.  Sure, we can slap two
files together; what the hell for?  Both are quite large, there's
a (relatively) sane separation of code between them (misc. files
contents in /proc/<pid>/ vs. directory structure and symlinks in
there, more or less) and I don't see any benefit in mashing them
together.  Up to Alexey, but IMO that's pointless.
--
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/