From: Peter Korsgaard <jacmet@sunsite.dk>
To: Greg KH <greg@kroah.com>
Cc: kay.sievers@vrfy.org, gregkh@suse.de,
linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org
Subject: Re: [PATCH] devtmpfs: support !CONFIG_TMPFS
Date: Tue, 16 Mar 2010 20:14:05 +0100 [thread overview]
Message-ID: <87wrxcgjuq.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20100316190005.GA32555@kroah.com> (Greg KH's message of "Tue, 16 Mar 2010 12:00:05 -0700")
>>>>> "Greg" == Greg KH <greg@kroah.com> writes:
Hi,
>> config DEVTMPFS
>> bool "Maintain a devtmpfs filesystem to mount at /dev"
>> - depends on HOTPLUG && SHMEM && TMPFS
>> + depends on HOTPLUG
>> help
>> This creates a tmpfs filesystem instance early at bootup.
>> In this filesystem, the kernel driver core maintains device
Greg> With this patch, the Kconfig help text now is incorrect.
Greg> Is there a way to explicitly call out in the Kconfig which way
Greg> devtmpfs is being created? How about a multiple selection that
Greg> chooses either TMPFS or RAMFS, with the default being TMPFS?
I don't think that's needed - If CONFIG_TMPFS isn't set, then ramfs
pretends to be tmpfs anyway, see mm/shmem.c:
static struct file_system_type tmpfs_fs_type = {
.name = "tmpfs",
.get_sb = ramfs_get_sb,
.kill_sb = kill_litter_super,
};
So calling it tmpfs isn't really wrong.
Greg> So care to redo this so that people can easily determine what is going
Greg> to happen easier than this patch currently causes?
We can change the help text to say tmpfs/ramfs if you prefer - OK?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-03-16 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 10:25 [PATCH] devtmpfs: support !CONFIG_TMPFS Peter Korsgaard
2010-03-12 11:28 ` Michael Tokarev
2010-03-12 11:38 ` Peter Korsgaard
2010-03-12 13:02 ` Kay Sievers
2010-03-16 13:04 ` Peter Korsgaard
2010-03-16 13:37 ` Greg KH
2010-03-16 19:00 ` Greg KH
2010-03-16 19:14 ` Peter Korsgaard [this message]
2010-03-16 20:17 ` Greg KH
2010-03-16 20:55 ` [PATCH-V2] " Peter Korsgaard
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=87wrxcgjuq.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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