From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: "Artem B. Bityutskiy" <dedekind@yandex.ru>
Cc: zhao forrest <zhao_fusheng@hotmail.com>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH]erase block header(revision 4)
Date: Mon, 3 Oct 2005 16:28:51 +0200 [thread overview]
Message-ID: <20051003142851.GE4639@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <43413716.1040402@yandex.ru>
On Mon, 3 October 2005 17:50:14 +0400, Artem B. Bityutskiy wrote:
> zhao forrest wrote:
> > Artem asked me to remove allocation on the stack, so who should I listen
> > to? This really made me very very confused :(
> Yes, I suggested to share one static clean-marker structure for both
> NAND and NOR cases.
Bad suggestion then. Try to draw a complete graph of all possible
users to this static structure, the locking required to make it
correct, then prove its correctness.
If that didn't already scare you to death, try to anticipate future
code changes to such brittle code.
In one word: don't.
> >> What was (c->cleanmarker_size == 0) used for?
> >
> > For the flash that don't need a clean marker.
> No, that worked for NAND this way (c->cleanmarker_size was 0)
So why is this part unnecessary now? Or should it just be replaced by
something else?
Jörn
--
Unless something dramatically changes, by 2015 we'll be largely
wondering what all the fuss surrounding Linux was really about.
-- Rob Enderle
next prev parent reply other threads:[~2005-10-03 14:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 13:40 [PATCH]erase block header(revision 4) zhao forrest
2005-10-03 13:50 ` Artem B. Bityutskiy
2005-10-03 14:28 ` Jörn Engel [this message]
2005-10-03 14:43 ` Artem B. Bityutskiy
2005-10-03 14:49 ` Jörn Engel
2005-10-09 6:08 ` zhao forrest
2005-10-09 7:06 ` Artem B. Bityutskiy
2005-10-09 10:35 ` Jörn Engel
2005-10-03 14:42 ` Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2005-09-28 7:33 zhao forrest
2005-09-30 1:15 ` root
2005-09-30 11:29 ` Jörn Engel
2005-10-03 11:23 ` Jörn Engel
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=20051003142851.GE4639@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=dedekind@yandex.ru \
--cc=linux-mtd@lists.infradead.org \
--cc=zhao_fusheng@hotmail.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