From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC/PATCH] ARM: dove: Remove UBI support from defconfig
Date: Mon, 27 Jan 2014 12:14:30 -0300 [thread overview]
Message-ID: <20140127151429.GB3036@localhost> (raw)
In-Reply-To: <20140127150040.GH29184@titan.lakedaemon.net>
On Mon, Jan 27, 2014 at 10:00:40AM -0500, Jason Cooper wrote:
> On Mon, Jan 27, 2014 at 10:26:29AM -0300, Ezequiel Garcia wrote:
> > As NAND support is not enabled by default, it's hard to see
> > why we'd want to have UBI support. Let's remove it.
>
> I'd rather add support for the nand.
>
Well, there isn't any Dove board (that we currently support) with a NAND
device. Would you still want to add it?
In that case, we should consider adding UBIFS as well. Having CONFIG_UBI
by itself doesn't make any sense.
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-27 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 13:26 [RFC/PATCH] ARM: dove: Remove UBI support from defconfig Ezequiel Garcia
2014-01-27 15:00 ` Jason Cooper
2014-01-27 15:14 ` Ezequiel Garcia [this message]
2014-01-27 15:19 ` Jason Cooper
2014-02-05 6:25 ` Jason Cooper
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=20140127151429.GB3036@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox