From: Andrew Morton <akpm@linux-foundation.org>
To: <chenjie6@huawei.com>
Cc: computersforpeace@gmail.com, lizefan@huawei.com,
linux-mtd@lists.infradead.org, David.Woodhouse@intel.com,
zengweilin@huawei.com
Subject: Re: [PATCH] [RESEND] jffs2: bugfix of summary length
Date: Thu, 18 Dec 2014 13:50:30 -0800 [thread overview]
Message-ID: <20141218135030.66660cb137ff34314c19449c@linux-foundation.org> (raw)
In-Reply-To: <1418900688-21760-1-git-send-email-chenjie6@huawei.com>
On Thu, 18 Dec 2014 19:04:48 +0800 <chenjie6@huawei.com> wrote:
> From: Chen Jie <chenjie6@huawei.com>
>
> sm->offset maybe wrong but magic maybe right, the offset
> do not have CRC.
How does this situation arise? Corrupted device contents?
next prev parent reply other threads:[~2014-12-18 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 11:04 [PATCH] [RESEND] jffs2: bugfix of summary length chenjie6
2014-12-18 21:50 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-11 19:03 chenjie6
2014-12-13 3:20 ` Brian Norris
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=20141218135030.66660cb137ff34314c19449c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=David.Woodhouse@intel.com \
--cc=chenjie6@huawei.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=lizefan@huawei.com \
--cc=zengweilin@huawei.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