From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jon Povey <Jon.Povey@racelogic.co.uk>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: mkfs.ubifs generating bad CRCs
Date: Wed, 01 Sep 2010 14:36:06 +0300 [thread overview]
Message-ID: <1283340966.1958.21.camel@brekeke> (raw)
In-Reply-To: <70E876B0EA86DD4BAF101844BC814DFE0903E02E09@Cloud.RL.local>
On Tue, 2010-08-31 at 11:57 +0100, Jon Povey wrote:
> Building mkfs.ubifs from today's mtd-utils git I get a mkfs.ubifs that seems to generate bad CRCs.
> I also have ubuntu's binary mtd-utils installed which produce good CRCs. I tested using both versions of mkfs.ubifs and only ubuntu's ubinize for both images, so can confirm ubinize is not a problem.
>
> Related sounding thing I found:
> http://lists.infradead.org/pipermail/linux-mtd/2010-July/031187.html
>
> After flashing the image from git mkfs.ubifs I get this on my console:
Fixed in current mtd-utils.git
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2010-09-01 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 10:57 mkfs.ubifs generating bad CRCs Jon Povey
2010-09-01 11:36 ` Artem Bityutskiy [this message]
2010-09-02 3:01 ` Jon Povey
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=1283340966.1958.21.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=Jon.Povey@racelogic.co.uk \
--cc=linux-mtd@lists.infradead.org \
/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