From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Mike Frysinger <vapier@gentoo.org>,
linux-mtd@lists.infradead.org, kernel@pengutronix.de,
Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH v4 1/2] mtd/uclinux: support ROM and allow passing the base address
Date: Thu, 17 Jan 2013 15:37:27 +0200 [thread overview]
Message-ID: <1358429847.2731.251.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1358347016-507-1-git-send-email-u.kleine-koenig@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 420 bytes --]
On Wed, 2013-01-16 at 15:36 +0100, Uwe Kleine-König wrote:
> This allows to put the filesystem at a defined address in ROM allowing
> to save more precious RAM.
>
> I think it's safe to default to ROM because the intention of using the
> uclinux map is to use a romfs and so mtd-ram doesn't give you anything
> that mtd-rom doesn't.
Pushed both to l2-mtd.git, thanks!
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-17 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 16:31 [PATCH 1/2 v3] mtd/uclinux: support ROM and allow passing the base address Uwe Kleine-König
2013-01-10 16:31 ` [PATCH 2/2 v3] mtd/uclinux: add a comment about why uclinux_ram_map must not be static Uwe Kleine-König
2013-01-11 13:37 ` [PATCH 1/2 v3] mtd/uclinux: support ROM and allow passing the base address Greg Ungerer
2013-01-11 14:02 ` Uwe Kleine-König
2013-01-12 11:42 ` Greg Ungerer
2013-01-16 14:36 ` [PATCH v4 1/2] " Uwe Kleine-König
2013-01-17 3:12 ` Greg Ungerer
2013-01-17 13:37 ` Artem Bityutskiy [this message]
2013-01-16 14:36 ` [PATCH v4 2/2] mtd/uclinux: add a comment about why uclinux_ram_map must not be static Uwe Kleine-König
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=1358429847.2731.251.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=gerg@uclinux.org \
--cc=kernel@pengutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vapier@gentoo.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.