From: Marco Stornelli <marco.stornelli@gmail.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Embedded <linux-embedded@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Tim Bird <tim.bird@am.sony.com>
Subject: Re: [PATCH 16/16] pramfs Makefile and Kconfig
Date: Mon, 11 Oct 2010 09:09:10 +0200 [thread overview]
Message-ID: <AANLkTinrRMDshtMQ_iBvRNYeEDQdihtu9ggu++masczR@mail.gmail.com> (raw)
In-Reply-To: <20101010100211.3c747512.rdunlap@xenotime.net>
2010/10/10 Randy Dunlap <rdunlap@xenotime.net>:
> On Sun, 10 Oct 2010 18:39:11 +0200 Marco Stornelli wrote:
>
>> From: Marco Stornelli <marco.stornelli@gmail.com>
>>
>> Makefile and Kconfig.
>>
>> Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
>> ---
>> diff -Nurp linux-2.6.36-orig/fs/pramfs/Kconfig linux-2.6.36/fs/pramfs/Kconfig
>> --- linux-2.6.36-orig/fs/pramfs/Kconfig 1970-01-01 01:00:00.000000000 +0100
>> +++ linux-2.6.36/fs/pramfs/Kconfig 2010-09-14 18:49:52.000000000 +0200
>> @@ -0,0 +1,72 @@
>> +config PRAMFS
>> + tristate "Persistent and Protected RAM file system support"
>> + depends on HAS_IOMEM && EXPERIMENTAL
>> + select CRC16
>> + help
>> + If your system has a block of fast (comparable in access speed to
>> + system memory) and non-volatile RAM and you wish to mount a
>> + light-weight, full-featured, and space-efficient filesystem over it,
>> + say Y here, and read <file:Documentation/filesystems/pramfs.txt>.
>> +
>> + To compile this as a module, choose M here: the module will be
>> + called pramfs.ko.
>
> called pramfs.
>
> (we don't add the .ko suffix; well, we try not to do that)
Ok.
>
>> +
>> +config PRAMFS_XIP
>> + bool "Enable Execute-in-place in PRAMFS"
>> + depends on PRAMFS && !PRAMFS_WRITE_PROTECT
>> + help
>> + Say Y here to enable xip feature of PRAMFS.
>
> XIP
Ok.
>
>> +
>> +config PRAMFS_WRITE_PROTECT
>> + bool "Enable PRAMFS write protection"
>> + depends on PRAMFS && MMU
>> + default y
>> + help
>> + Say Y here to enable the write protect feature of PRAMFS.
>> +
>> +config PRAMFS_XATTR
>> + bool "PRAMFS extended attributes"
>> + depends on PRAMFS
>> + help
>> + Extended attributes are name:value pairs associated with inodes by
>> + the kernel or by users (see the attr(5) manual page, or visit
>> + <http://acl.bestbits.at/> for details).
>> +
>> + If unsure, say N.
>> +
>> +config PRAMFS_POSIX_ACL
>> + bool "PRAMFS POSIX Access Control Lists"
>> + depends on PRAMFS_XATTR
>> + select FS_POSIX_ACL
>> + help
>> + Posix Access Control Lists (ACLs) support permissions for users and
>> + groups beyond the owner/group/world scheme.
>> +
>> + To learn more about Access Control Lists, visit the Posix ACLs for
>> + Linux website <http://acl.bestbits.at/>.
>> +
>> + If you don't know what Access Control Lists are, say N
>
> end sentence with period ('.').
Ok.
prev parent reply other threads:[~2010-10-11 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 16:39 [PATCH 16/16] pramfs Makefile and Kconfig Marco Stornelli
2010-10-10 17:02 ` Randy Dunlap
2010-10-11 7:09 ` Marco Stornelli [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=AANLkTinrRMDshtMQ_iBvRNYeEDQdihtu9ggu++masczR@mail.gmail.com \
--to=marco.stornelli@gmail.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=tim.bird@am.sony.com \
/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).