linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Wolfgang Wegner <wolfgang@leila.ping.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS oops after remount ro
Date: Thu, 02 Dec 2010 05:41:01 +0200	[thread overview]
Message-ID: <1291261261.14534.7.camel@koala> (raw)
In-Reply-To: <1291260934.14534.6.camel@koala>

On Thu, 2010-12-02 at 05:35 +0200, Artem Bityutskiy wrote:
> On Mon, 2010-11-29 at 18:02 +0100, Wolfgang Wegner wrote:
> > Hi Artem,
> > 
> > On Mon, Nov 29, 2010 at 06:45:57PM +0200, Artem Bityutskiy wrote:
> > > 
> > > I cannot judge for sure, but this looks like non-UBIFS issue in 2.6.32,
> > > so merging the stable 2.6.32.X tree can help. I make sense in general to
> > > merge stable tree as well.
> > 
> > the problem is I still have some "marvell" tree
> > (from git.marvell.com/orion.git) and am not sure if there is anything
> > special in it.
> 
> Mostly vendors change drivers and board files. They usually do not touch
> core functionality. So you can try to merge 2.6.32

Err, I meant 2.6.32.x, of course, the so-called -stable tree which Greg
KH maintains.

-- 
Best Regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2010-12-02  3:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-26 13:50 UBIFS oops after remount ro Wolfgang Wegner
2010-11-26 15:24 ` Artem Bityutskiy
2010-11-26 17:29   ` Wolfgang Wegner
2010-11-29 13:18   ` Wolfgang Wegner
2010-11-29 14:21     ` Artem Bityutskiy
     [not found]       ` <20101129151729.GE23237@leila.ping.de>
     [not found]         ` <1291049157.2141.17.camel@koala>
2010-11-29 17:02           ` Wolfgang Wegner
2010-11-29 17:23             ` Wolfgang Wegner
2010-12-02  3:35             ` Artem Bityutskiy
2010-12-02  3:41               ` Artem Bityutskiy [this message]
2010-12-02  9:17               ` Wolfgang Wegner
2010-12-02 12:20                 ` 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=1291261261.14534.7.camel@koala \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=wolfgang@leila.ping.de \
    /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).