From: Marco Stornelli <marco.stornelli@gmail.com>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
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:58:55 +0100 [thread overview]
Message-ID: <4D25F4CF.1030009@gmail.com> (raw)
In-Reply-To: <4D25ED22.3070900@gmail.com>
Il 06/01/2011 17:26, Marco Stornelli ha scritto:
> Il 06/01/2011 15:03, Peter Zijlstra ha scritto:
> and temporary information with a complete fs structure. However we are
>
Errata corrige: maybe I used the wrong term, I meant "volatile" instead
of "temporary" information, i.e. I'd like to save this info to re-read
it later but I don't want to store it in flash, a simple log, run-time
information for debug like a flight-recorder or whatever you want.
next prev parent reply other threads:[~2011-01-06 16:58 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
2011-01-06 16:58 ` Marco Stornelli [this message]
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=4D25F4CF.1030009@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.