From: Ferenc Havasi <havasi@inf.u-szeged.hu>
To: zhao forrest <zhao_fusheng@hotmail.com>
Cc: dedekind@yandex.ru, linux-mtd@lists.infradead.org
Subject: Re: [PATCH]Erase block header(revision 1)
Date: Fri, 23 Sep 2005 11:29:23 +0200 [thread overview]
Message-ID: <4333CAF3.3070004@inf.u-szeged.hu> (raw)
In-Reply-To: <BAY17-F141EA92F45DB70328CE1C5E8960@phx.gbl>
Hi Zhao,
First of all: your implementation of EBH summary support a good job,
congratulation!
I noticed only two things:
+ case JFFS2_NODETYPE_ERASEBLOCK_HEADER:
+ s->sum_size +=
JFFS2_SUMMARY_EBH_SIZE(je16_to_cpu(item->eh.dsize)*4);
Here I think you should use sizeof(uint32_t) instead of simple 4, as you
used it otherwhere. I's a very small thing, I know.
The other is related to it: if I were you I would store eh.dsize in
bytes, not in uint32. In every other places of JFFS2 the size is stored
byte based (if I am right), and there is no need to always multible by
sizeof(uint32_t) if the real size is needed.
I have only one big problem with this patch. I'm strongly against to
introduce INCOMPAT nodes JFFS2_NODETYPE_DIRENT_EBH and
JFFS2_NODETYPE_INODE_EBH just to make unusable new JFFS2 images for old
JFFS2 code on NAND devices, too. Do I understand well: is this the only
reason?
Ferenc
next parent reply other threads:[~2005-09-23 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY17-F141EA92F45DB70328CE1C5E8960@phx.gbl>
2005-09-23 9:29 ` Ferenc Havasi [this message]
2005-09-23 9:33 ` [PATCH]Erase block header(revision 1) Artem B. Bityutskiy
2005-09-23 10:24 ` zhao forrest
2005-09-25 11:04 ` Jörn Engel
2005-09-26 8:02 ` zhao forrest
2005-09-26 8:19 ` Jörn Engel
2005-09-26 9:08 ` Artem B. 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=4333CAF3.3070004@inf.u-szeged.hu \
--to=havasi@inf.u-szeged.hu \
--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