From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: Rodrigo Freire <rfreire@redhat.com>
Cc: "Felix Fietkau" <nbd@openwrt.org>, "Jörn Engel" <joern@logfs.org>,
"Herton Krzesinski" <hkrzesin@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"David Woodhouse" <dwmw2@infradead.org>
Subject: Re: [PATCH V2] mtd: block2mtd: Present block2mtd timely on boot time
Date: Wed, 17 Sep 2014 22:21:37 +0100 [thread overview]
Message-ID: <CAAEAJfDAG8KrPKqVC5NujGnbSyxmrAtFcLvhScYsNm8RT59Gnw@mail.gmail.com> (raw)
In-Reply-To: <1807144344.40128259.1410985683342.JavaMail.zimbra@redhat.com>
On 17 September 2014 21:28, Rodrigo Freire <rfreire@redhat.com> wrote:
>
> mtd: block2mtd: Ensure that block2mtd is presented in a timely fashion
>
Using block2mtd sounds a bit unusual. I see that you are trying to get
a more robust fs.... have you tried using f2fs instead of jffs2?
> Currently, a block MTD device is not presented to the system on time, in
> order to start mounting the filesystems. This patch ensures that block2mtd
> is presented at the right time, so filesystems can be mounted on boot time.
It worries me a bit to add such a long delay to the boot. If for some
reason the SD is not working, then the kernel will wait (by default) 3
seconds now?
--
Ezequiel García, VanguardiaSur
www.vanguardiasur.com.ar
next prev parent reply other threads:[~2014-09-17 21:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <371358190.34795877.1410204429882.JavaMail.zimbra@redhat.com>
2014-09-08 20:04 ` [PATCH] block2mtd: mtd: Present block2mtd timely on boot time Rodrigo Freire
2014-09-09 17:02 ` Jörn Engel
2014-09-17 20:18 ` Rodrigo Freire
2014-09-17 20:28 ` [PATCH V2] mtd: block2mtd: " Rodrigo Freire
2014-09-17 21:21 ` Ezequiel Garcia [this message]
2014-09-17 21:41 ` Rodrigo Freire
2014-10-09 15:07 ` [RESEND PATCH " Rodrigo Freire
2014-11-01 13:33 ` Rodrigo Freire
2014-11-07 9:44 ` Artem Bityutskiy
2014-11-07 20:05 ` Brian Norris
2014-11-05 20:01 ` Brian Norris
2014-11-05 20:23 ` [PATCH " Brian Norris
2014-11-07 14:59 ` Artem Bityutskiy
2014-11-07 15:20 ` Felix Fietkau
2014-11-07 15:30 ` Artem Bityutskiy
2014-11-09 12:18 ` Rodrigo Freire
2014-11-26 3:33 ` Brian Norris
2014-11-26 13:32 ` Rodrigo Freire
2015-02-11 15:09 ` Rodrigo Freire
2014-11-09 12:18 ` [PATCH v3 0/3] mtd: block2mtd: wait for device enumeration, add name support Rodrigo Freire
2014-11-09 12:21 ` [PATCH v3 1/3] mtd: block2mtd: Ensure that block2mtd is triggered after block devices are presented Rodrigo Freire
2015-02-24 7:45 ` Brian Norris
2014-11-09 12:22 ` [PATCH v3 2/3] mtd: block2mtd: Adds a mtd name and a block device timeout option Rodrigo Freire
2015-02-24 8:05 ` Brian Norris
2014-11-09 12:23 ` [PATCH v3 3/3] mtd: block2mtd: Removes PAGE_MASK as a index to partition size Rodrigo Freire
2014-11-26 7:21 ` Brian Norris
2014-11-26 13:19 ` Rodrigo Freire
2015-02-24 8:07 ` Brian Norris
2015-02-24 8:20 ` Felix Fietkau
2015-02-24 8:27 ` Brian Norris
2015-02-24 8:30 ` Felix Fietkau
2015-02-24 8:40 ` Brian Norris
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=CAAEAJfDAG8KrPKqVC5NujGnbSyxmrAtFcLvhScYsNm8RT59Gnw@mail.gmail.com \
--to=ezequiel@vanguardiasur.com.ar \
--cc=dwmw2@infradead.org \
--cc=hkrzesin@redhat.com \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nbd@openwrt.org \
--cc=rfreire@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).