All of lore.kernel.org
 help / color / mirror / Atom feed
From: wolfgang@leila.ping.de (Wolfgang Wegner)
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS oops after remount ro
Date: Mon, 29 Nov 2010 18:02:23 +0100	[thread overview]
Message-ID: <20101129170223.GF23237@leila.ping.de> (raw)
In-Reply-To: <1291049157.2141.17.camel@koala>

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.

Would the "stock" 2.6.35.x from
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
be an option in your opinion, too? I seem to remember the marvell tree
was completely merged in between (right now digging through the commits
to make it clear), so I could get an all shiny, new kernel when having
to do any kind of merge at all...

Regards,
Wolfgang

  parent reply	other threads:[~2010-11-29 17:13 UTC|newest]

Thread overview: 12+ 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 [this message]
2010-11-29 17:23             ` Wolfgang Wegner
2010-12-02  3:35             ` Artem Bityutskiy
2010-12-02  3:41               ` Artem Bityutskiy
2010-12-02  9:17               ` Wolfgang Wegner
2010-12-02 12:20                 ` Artem Bityutskiy
  -- strict thread matches above, loose matches on Subject: below --
2010-11-23 14:44 Wolfgang Wegner

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=20101129170223.GF23237@leila.ping.de \
    --to=wolfgang@leila.ping.de \
    --cc=dedekind1@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.