From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Linux MTD <linux-mtd@lists.infradead.org>,
Peter Menzebach <pm-mtd@mw-itcon.de>
Subject: Re: Minimum/optimal sector_size for jffs2
Date: Mon, 26 Sep 2005 12:56:41 +0400 [thread overview]
Message-ID: <4337B7C9.6030402@yandex.ru> (raw)
In-Reply-To: <20050925151550.GE28978@wohnheim.fh-wedel.de>
Jörn Engel wrote:
> Hmm. "sector_size" is a confusing name. It reminds people of a disk
> sector, which is semantically similar to the writesize (or pagesize,
> if NAND people prefer). But JFFS2 uses sector_size as erasesize.
>
I would not mind if one rename that field to erasesize.
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2005-09-26 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 9:51 Minimum/optimal sector_size for jffs2 Peter Menzebach
2005-09-23 10:05 ` Artem B. Bityutskiy
2005-09-23 11:30 ` Peter Menzebach
2005-09-25 15:15 ` Jörn Engel
2005-09-26 8:56 ` Artem B. Bityutskiy [this message]
2005-09-27 14:59 ` Artem B. Bityutskiy
2005-09-27 17:54 ` Peter Menzebach
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=4337B7C9.6030402@yandex.ru \
--to=dedekind@yandex.ru \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.org \
--cc=pm-mtd@mw-itcon.de \
/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