From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 19 (devtmpfs build error)
Date: Tue, 19 May 2009 08:58:51 -0700 [thread overview]
Message-ID: <20090519085851.3b8386ed.rdunlap@xenotime.net> (raw)
In-Reply-To: <20090519183044.a910aa7a.sfr@canb.auug.org.au>
On Tue, 19 May 2009 18:30:44 +1000 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20090518:
when CONFIG_SHMEM=n:
drivers/built-in.o: In function `dev_get_sb':
devtmpfs.c:(.text+0x13263b): undefined reference to `shmem_fill_super'
---
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/
next prev parent reply other threads:[~2009-05-19 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 8:30 linux-next: Tree for May 19 Stephen Rothwell
2009-05-19 13:06 ` make clean drivers/staging/cpc_usb fails on " Nico -telmich- Schottelius
2009-05-19 15:58 ` Randy Dunlap [this message]
2009-05-20 18:56 ` linux-next: Tree for May 19 (devtmpfs build error) Kay Sievers
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=20090519085851.3b8386ed.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).