From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randy Dunlap Subject: Re: linux-next: Tree for May 26 (drivers/base/node.c) Date: Fri, 10 Jun 2011 12:53:38 -0700 Message-ID: <4DF27642.1080208@oracle.com> References: <20110526163941.7dfcad1a.sfr@canb.auug.org.au> <20110526120121.db0506de.randy.dunlap@oracle.com> <20110610084405.c34a166d.randy.dunlap@oracle.com> <20110610183108.GB10575@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110610183108.GB10575@kroah.com> Sender: linux-kernel-owner@vger.kernel.org To: Greg KH Cc: Stephen Rothwell , linux-next@vger.kernel.org, LKML List-Id: linux-next.vger.kernel.org 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 ***