From: Greg KH <greg@kroah.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: linux-next: Tree for May 1 (devtmpfs)
Date: Fri, 1 May 2009 15:56:16 -0700 [thread overview]
Message-ID: <20090501225616.GA18064@kroah.com> (raw)
In-Reply-To: <20090501165551.GA1889@puku.stupidest.org>
On Fri, May 01, 2009 at 09:55:52AM -0700, Chris Wedgwood wrote:
> On Fri, May 01, 2009 at 08:28:33AM -0700, Randy Dunlap wrote:
>
> > drivers/base/devtmpfs.c:41: error: implicit declaration of function 'vfs_mkdir'
> > drivers/base/devtmpfs.c:46: error: dereferencing pointer to incomplete type
>
> [...]
>
> Why is devtmpfs in linux-next? My read of the thread so far seems to
> indicate there is considerable uncertainty that this is necessary or
> desirable.
As we discussed on irc, I think you no longer object to this, and see
how it solves a real problem, and can probably help out your initramfs
tools.
So it should stay in -next for now, and see if any build/use problems
happen with it. I've been running it all this week on my machines just
fine.
thanks,
greg k-h
next prev parent reply other threads:[~2009-05-01 23:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 6:34 linux-next: Tree for May 1 Stephen Rothwell
2009-05-01 15:18 ` linux-next: Tree for May 1 (tmpfs) Randy Dunlap
2009-05-02 5:24 ` Stephen Rothwell
2009-05-01 15:25 ` linux-next: Tree for May 1 (comedi) Randy Dunlap
2009-05-01 15:28 ` linux-next: Tree for May 1 (devtmpfs) Randy Dunlap
2009-05-01 16:51 ` Kay Sievers
2009-05-01 16:55 ` Chris Wedgwood
2009-05-01 22:56 ` Greg KH [this message]
2009-05-02 7:01 ` Christoph Hellwig
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=20090501225616.GA18064@kroah.com \
--to=greg@kroah.com \
--cc=cw@f00f.org \
--cc=kay.sievers@vrfy.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox