From: Marco Stornelli <marco.stornelli@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux Embedded <linux-embedded@vger.kernel.org>,
Tim Bird <tim.bird@am.sony.com>, Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH 00/17] pramfs: persistent and protected RAM filesystem
Date: Thu, 06 Jan 2011 17:26:10 +0100 [thread overview]
Message-ID: <4D25ED22.3070900@gmail.com> (raw)
In-Reply-To: <1294322613.2016.333.camel@laptop>
Il 06/01/2011 15:03, Peter Zijlstra ha scritto:
> On Thu, 2011-01-06 at 13:00 +0100, Marco Stornelli wrote:
>> Hi all,
>>
>> after several reviews is time to submit the code for mainline. Thanks to
>> CELF to believe and support actively the project and thanks to Tim Bird.
>
> Tony Luck was also playing with something like this I believe.
>
Yes, I know. Even if the approach is different. He is trying to use a
persistent space record-based and with a simple fs interface to store
oops or something like this. The idea here is a little bit different,
i.e. to have a place (a generic piece of memory) to write not sensible
and temporary information with a complete fs structure. However we are
on the same road :)
Marco
next prev parent reply other threads:[~2011-01-06 16:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 12:00 [PATCH 00/17] pramfs: persistent and protected RAM filesystem Marco Stornelli
2011-01-06 14:03 ` Peter Zijlstra
2011-01-06 16:26 ` Marco Stornelli [this message]
2011-01-06 16:58 ` Marco Stornelli
2011-01-06 18:22 ` Luck, Tony
2011-01-06 18:31 ` Marco Stornelli
2011-01-11 13:33 ` Pavel Machek
2011-01-11 19:01 ` Marco Stornelli
-- strict thread matches above, loose matches on Subject: below --
2012-06-10 9:13 Marco Stornelli
2012-06-10 11:20 ` Christian Stroetmann
2012-06-11 6:28 ` Marco Stornelli
2012-06-13 18:57 ` Florian Weimer
2012-06-14 6:17 ` Marco Stornelli
2012-06-14 6:17 ` Marco Stornelli
2012-06-16 6:57 ` Marco
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=4D25ED22.3070900@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=peterz@infradead.org \
--cc=tim.bird@am.sony.com \
--cc=tony.luck@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.