From: Greg KH <greg@kroah.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 26 (drivers/base/node.c)
Date: Fri, 10 Jun 2011 11:31:08 -0700 [thread overview]
Message-ID: <20110610183108.GB10575@kroah.com> (raw)
In-Reply-To: <20110610084405.c34a166d.randy.dunlap@oracle.com>
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.
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?
thanks,
greg k-h
next prev parent reply other threads:[~2011-06-10 18:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 6:39 linux-next: Tree for May 26 Stephen Rothwell
2011-05-26 19:01 ` linux-next: Tree for May 26 (drivers/base/node.c) Randy Dunlap
2011-06-10 15:44 ` Randy Dunlap
2011-06-10 18:31 ` Greg KH [this message]
2011-06-10 19:53 ` Randy Dunlap
2011-05-26 19:07 ` linux-next: Tree for May 26 (drivers/net/caif) Randy Dunlap
2011-05-26 21:15 ` Sjur Brændeland
2011-05-26 21:30 ` Randy Dunlap
2011-05-27 8:09 ` [PATCH] caif: Fix compile warning in caif_serial.c Sjur Brændeland
2011-05-27 15:37 ` Randy Dunlap
2011-05-27 1:01 ` linux-next: Tree for May 26 (drivers/net/caif) Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110610183108.GB10575@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.