From: Kay Sievers <kay.sievers@vrfy.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartmann <greg@kroah.com>
Subject: Re: linux-next: Tree for May 19 (devtmpfs build error)
Date: Wed, 20 May 2009 20:56:16 +0200 [thread overview]
Message-ID: <ac3eb2510905201156l43ad44d4l358c7f87159fd82e@mail.gmail.com> (raw)
In-Reply-To: <20090519085851.3b8386ed.rdunlap@xenotime.net>
On Tue, May 19, 2009 at 17:58, Randy Dunlap <rdunlap@xenotime.net> wrote:
> On Tue, 19 May 2009 18:30:44 +1000 Stephen Rothwell wrote:
>> 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'
Needed dependencies added.
Thanks,
Kay
prev parent reply other threads:[~2009-05-20 18: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 ` linux-next: Tree for May 19 (devtmpfs build error) Randy Dunlap
2009-05-20 18:56 ` Kay Sievers [this message]
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=ac3eb2510905201156l43ad44d4l358c7f87159fd82e@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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).