From: Artem Bityutskiy <dedekind1@gmail.com>
To: Karsten Jeppesen <arm9263@yahoo.com>
Cc: ubifs <linux-mtd@lists.infradead.org>
Subject: Re: Corrupted UBIFS, bad CRC
Date: Mon, 16 Jan 2012 14:46:07 +0200 [thread overview]
Message-ID: <1326717967.14299.77.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1326717654.83444.YahooMailNeo@web121506.mail.ne1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
On Mon, 2012-01-16 at 04:40 -0800, Karsten Jeppesen wrote:
> Hi Artem,
>
> OO something bad happened here. We must have lost track of each other.
>
> What I sent you was ***NOT*** produced by our standard 2.6.32.8 kernel.
> I spent quite some efforts in adapting the new 3.2.0 kernel.
Well, ok, does not matter anyway.
> I wrote that in my original email, but you may have drifted off to the emails from November.
> To make life easier for you I assumed you would rather look at data including the newest stuff rather than backported stuff.
There are few fixes for 3.2 in ubifs-v3.2 tree. Namely, they make
UBI/UBIFS print some debugging message which are not printed otherwise,
due to a bug I introduced at 3.0 times. Please, pick them.
Please, just substitute s/2.6.32/3.2/ in my reply.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-16 12:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 13:47 Corrupted UBIFS, bad CRC Karsten Jeppesen
2012-01-15 12:24 ` Artem Bityutskiy
2012-01-16 8:18 ` Karsten Jeppesen
2012-01-16 10:24 ` Artem Bityutskiy
2012-01-16 12:40 ` Karsten Jeppesen
2012-01-16 12:46 ` Artem Bityutskiy [this message]
2012-01-16 12:50 ` Artem Bityutskiy
2012-01-17 12:23 ` Karsten Jeppesen
2012-01-18 14:43 ` Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2012-01-12 14:31 Karsten Jeppesen
2011-11-23 12:49 Karsten Jeppesen
2011-11-29 21:58 ` Artem 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=1326717967.14299.77.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=arm9263@yahoo.com \
--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