From: "Artem B. Bityuckiy" <dedekind@yandex.ru>
To: zhao forrest <zhao_fusheng@hotmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Should we put jffs2_sum_marker into eraseblock_header?
Date: Tue, 13 Sep 2005 14:42:53 +0400 [thread overview]
Message-ID: <4326AD2D.2070203@yandex.ru> (raw)
In-Reply-To: <BAY17-F5764D8A5D6C706B910F94E89C0@phx.gbl>
zhao forrest wrote:
> Hi,
>
> When writing the eraseblock_header patch, I found the current
> summary patch in MTD CVS place jffs2_sum_marker at the end of
> each erase block. Since jffs2_sum_marker is a per-eraseblock
> structure, should we put it into eraseblock_header when the
> eraseblock_header patch is ready in the future?
>
Yes, it ought to go there IMO.
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2005-09-13 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 10:39 Should we put jffs2_sum_marker into eraseblock_header? zhao forrest
2005-09-13 10:42 ` Artem B. Bityuckiy [this message]
2005-09-13 10:46 ` Jörn Engel
2005-09-13 11:59 ` Ferenc Havasi
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=4326AD2D.2070203@yandex.ru \
--to=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