From: Artem Bityutskiy <dedekind1@gmail.com>
To: Reginald Perrin <reggyperrin@yahoo.com>
Cc: MTD Mailing List <linux-mtd@lists.infradead.org>
Subject: Re: Back-porting latest code to Blackfin 2.6.34.7-ADI-2010R1
Date: Fri, 09 Dec 2011 00:00:35 +0200 [thread overview]
Message-ID: <1323381636.2074.7.camel@koala> (raw)
In-Reply-To: <1323278916.12142.YahooMailNeo@web114614.mail.gq1.yahoo.com>
On Wed, 2011-12-07 at 09:28 -0800, Reginald Perrin wrote:
> Hi folks,
>
> We're using 2.6.34.7 from ADI without modification (meaning ADI's version). When I check this version against the ubifs-v2.6.34.git that's the "official" version, there are definitely differences.
>
> Does anybody know the status of the .34 tree and the reliability (I'm asking this same question @ ADI)? Specifically, we're fighting corruption issues, trying to track down what might be corrupting the LEB structure.
Hi,
I think if you pull the back-port tree, than all kernel versions
should be the same in terms of reliability of UBI/UBIFS.
Artem.
prev parent reply other threads:[~2011-12-08 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 17:28 Back-porting latest code to Blackfin 2.6.34.7-ADI-2010R1 Reginald Perrin
2011-12-08 22:00 ` Artem Bityutskiy [this message]
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=1323381636.2074.7.camel@koala \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=reggyperrin@yahoo.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;
as well as URLs for NNTP newsgroup(s).