linux-kernel - Re: linux-next: Tree for May 26 (drivers/base/node.c)

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

Message-ID: <4DF27642.1080208@oracle.com>
Date:	Fri, 10 Jun 2011 12:53:38 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Greg KH <greg@...ah.com>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for May 26 (drivers/base/node.c)

On 06/10/11 11:31, Greg KH wrote:
> On Fri, Jun 10, 2011 at 08:44:05AM -0700, Randy Dunlap wrote:
>> On Thu, 26 May 2011 12:01:21 -0700 Randy Dunlap wrote:
>>
>>> On Thu, 26 May 2011 16:39:41 +1000 Stephen Rothwell wrote:
>>>
>>>> Hi all,
>>>>
>>>> [The kernel.org mirroring is being slow today]
>>>
>>>
>>> when CONFIG_PROC_FS is not enabled:
>>>
>>> drivers/built-in.o: In function `node_read_vmstat':
>>> node.c:(.text+0x56ffa): undefined reference to `vmstat_text'
>>
>> Hi Greg,
>>
>> How do you want this build problem fixed?  (still around in
>> linux-next-20110610)
> 
> A patch would be great.

Yes, I was looking for general suggestions about such a patch,
but I'll just submit one and you can comment on it.

> But honestly, I really find that CONFIG_PROC_FS disabled to not be a
> valid configuration anymore.  I don't know anyone who can successfully
> run a machine in that manner, do you?

then why don't you submit a patch to remove that config option?
We could use fewer config options IMO.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your 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/