From: Tim Bird <tim.bird@am.sony.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Chris Simmonds <chris@2net.co.uk>, Arnd Bergmann <arnd@arndb.de>,
Marco <marco.stornelli@gmail.com>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux Embedded <linux-embedded@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 06/14] Pramfs: Include files
Date: Mon, 22 Jun 2009 15:00:55 -0700 [thread overview]
Message-ID: <4A3FFF17.9020701@am.sony.com> (raw)
In-Reply-To: <20090622203034.GA12587@uranus.ravnborg.org>
Sam Ravnborg wrote:
> It is not that we are talking big and complex stuff here.
I agree completely.
> pramfs is likely to be used for small things and then having to
> fix endian on a few headers in the on-dsk format does not matter.
I agree with this, but mostly out of exhaustion.
> Not compared to the potential disadvantages.
I can see no potential disadvantages.
> It should be possible to read a file-system on your x86 64bit
> box that you wrote with your small powerpc target.
For a (NV)RAM-based filesystem?? WTH???
This is not my file system, so I don't have a dog in this
fight. I just wanted to clarify what I thought were some
misconceptions about the use cases and priorities for the
FS. My "advocacy" may be interfering with understanding
this system and its purpose. I'll be quiet now.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================
next prev parent reply other threads:[~2009-06-22 22:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 13:21 [PATCH 06/14] Pramfs: Include files Marco
2009-06-13 14:04 ` Sam Ravnborg
2009-06-13 22:59 ` Arnd Bergmann
2009-06-14 7:15 ` Marco
2009-06-21 17:07 ` Marco
2009-06-21 20:22 ` Arnd Bergmann
2009-06-22 6:23 ` Marco Stornelli
2009-06-22 6:23 ` Marco Stornelli
2009-06-22 11:17 ` Arnd Bergmann
2009-06-22 18:05 ` Marco
2009-06-22 18:33 ` Arnd Bergmann
2009-06-22 19:31 ` Chris Simmonds
2009-06-22 20:30 ` Sam Ravnborg
2009-06-22 22:00 ` Tim Bird [this message]
2009-06-23 4:21 ` Sam Ravnborg
2009-06-23 17:38 ` Marco
2009-06-23 19:26 ` Jörn Engel
2009-06-23 19:26 ` Jörn Engel
2009-06-23 21:15 ` David Woodhouse
2009-06-23 21:15 ` David Woodhouse
2009-06-23 21:55 ` Arnd Bergmann
2009-06-24 6:32 ` Marco Stornelli
2009-06-24 15:30 ` Arnd Bergmann
2009-06-24 16:49 ` Marco
2009-06-22 21:41 ` Jörn Engel
2009-06-22 21:41 ` Jörn Engel
2009-06-22 22:20 ` David Woodhouse
2009-06-22 22:20 ` David Woodhouse
2009-06-22 22:20 ` David Woodhouse
2009-06-23 5:57 ` Jörn Engel
2009-06-23 8:31 ` David Woodhouse
2009-06-23 8:31 ` David Woodhouse
2009-06-23 8:31 ` David Woodhouse
2009-06-22 23:07 ` Arnd Bergmann
2009-06-22 23:07 ` Arnd Bergmann
2009-06-22 23:07 ` Arnd Bergmann
2009-06-23 6:40 ` Marco Stornelli
2009-06-23 6:40 ` Marco Stornelli
2009-06-14 7:15 ` 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=4A3FFF17.9020701@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=arnd@arndb.de \
--cc=chris@2net.co.uk \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=sam@ravnborg.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 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.