From: Jamie Lokier <jamie@shareable.org>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>,
linux-mtd@lists.infradead.org
Subject: Re: [RFC/PATCH] flash_eraseall: extra care if NOR flash is not BIT_WRITEABLE
Date: Thu, 26 Mar 2009 13:44:18 +0000 [thread overview]
Message-ID: <20090326134418.GB21993@shareable.org> (raw)
In-Reply-To: <1237962807.14602.99.camel@localhost.localdomain>
Artem Bityutskiy wrote:
> It sounds wrong to me to make flash_eraseall depend on how JFFS2 is
> compiled...
It sounds wrong to me as well.
What if you're running flash_eraseall on one kernel - it might not
even have JFFS2 - and then use the flash later with a different kernel
with a different setting.
-- Jamie
next prev parent reply other threads:[~2009-03-26 13:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 22:42 mtd-utils/flash_eraseall: tiny cleanup Sebastian Andrzej Siewior
2009-03-23 22:42 ` [PATCH] flash_eraseall: create two functions from existing code Sebastian Andrzej Siewior
2009-03-23 22:42 ` [PATCH] flash_eraseall: only add cleanmarkers on known flashtypes Sebastian Andrzej Siewior
2009-03-24 6:02 ` Artem Bityutskiy
2009-03-24 6:03 ` Artem Bityutskiy
2009-03-23 22:42 ` [RFC/PATCH] flash_eraseall: extra care if NOR flash is not BIT_WRITEABLE Sebastian Andrzej Siewior
2009-03-24 6:05 ` Artem Bityutskiy
2009-03-24 8:55 ` Sebastian Andrzej Siewior
2009-03-25 6:33 ` Artem Bityutskiy
2009-03-26 13:44 ` Jamie Lokier [this message]
2009-03-26 15:41 ` Sebastian Andrzej Siewior
2009-03-26 15:54 ` Ricard Wanderlof
2009-04-05 19:43 ` Sebastian Andrzej Siewior
2009-04-06 8:09 ` Ricard Wanderlof
2009-03-27 5:55 ` Artem Bityutskiy
2009-04-05 20:07 ` Sebastian Andrzej Siewior
2009-04-06 9:29 ` Artem Bityutskiy
2009-04-06 9:32 ` Artem Bityutskiy
2009-04-10 12:30 ` Artem Bityutskiy
2009-08-06 14:58 ` Sebastian Andrzej Siewior
2009-08-09 5:20 ` Artem Bityutskiy
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=20090326134418.GB21993@shareable.org \
--to=jamie@shareable.org \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sebastian@breakpoint.cc \
/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.