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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 11 Jun 2009 09:15:05 +0800
From:	Amerigo Wang <amwang@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Al Viro <viro@...IV.linux.org.uk>, linux-kernel@...r.kernel.org,
	Alexey Dobriyan <adobriyan@...il.com>
Subject: Re: 2.6.31 -mm merge plans

Andrew Morton wrote:
> (cc's added)
>
> On Wed, 10 Jun 2009 20:08:41 +0100
> Al Viro <viro@...IV.linux.org.uk> wrote:
>
>   
>> 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.
>>     
>
> No strong opinions here.
>   

Hi, Al.

Just as what I said in the description of that patch, one only has 
extern functions that are _only_ used in another as function pointers.

And the size of code can't be a reason why they are seperated, we have
much more source files larger than this one. :)

Thanks.


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