lkml.org 
[lkml]   [2010]   [Mar]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] devtmpfs: support !CONFIG_TMPFS
    On Fri, Mar 12, 2010 at 11:25:04AM +0100, Peter Korsgaard wrote:
    > Make devtmpfs available on (embedded) configurations without SHMEM/TMPFS,
    > using ramfs instead.
    >
    > Saves ~15KB.
    >
    > Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
    > ---
    > drivers/base/Kconfig | 2 +-
    > drivers/base/devtmpfs.c | 5 +++++
    > fs/ramfs/inode.c | 2 +-
    > include/linux/ramfs.h | 2 ++
    > 4 files changed, 9 insertions(+), 2 deletions(-)
    >
    > diff --git a/drivers/base/Kconfig b/drivers/base/Kconfig
    > index fd52c48..7e33b16 100644
    > --- a/drivers/base/Kconfig
    > +++ b/drivers/base/Kconfig
    > @@ -18,7 +18,7 @@ config UEVENT_HELPER_PATH
    >
    > 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

    With this patch, the Kconfig help text now is incorrect.
    Is there a way to explicitly call out in the Kconfig which way devtmpfs
    is being created? How about a multiple selection that chooses either
    TMPFS or RAMFS, with the default being TMPFS?

    So care to redo this so that people can easily determine what is going
    to happen easier than this patch currently causes?

    thanks,

    greg k-h


    \
     
     \ /
      Last update: 2010-03-16 20:11    [W:0.020 / U:91.724 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site