From: Artem Bityutskiy <dedekind1@gmail.com>
To: Charles Manning <manningc2@actrix.gen.nz>
Cc: linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: UBIFS not mounting on linux-omap 2.6.36
Date: Tue, 21 Dec 2010 19:36:22 +0200 [thread overview]
Message-ID: <1292952982.13362.21.camel@koala> (raw)
In-Reply-To: <201012201118.01766.manningc2@actrix.gen.nz>
On Mon, 2010-12-20 at 11:18 +1300, Charles Manning wrote:
> Hi All
>
> I am trying to nail down an omap3 ubifs performance regression, but cannot
> get Steve Sakoman's 2.6.35 or 2.6.36 kernels
> http://www.sakoman.com/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git
> to mount ubifs although the same procedure works with older kernels and works
> with the linux-omap 2.6.37 master.
Well, the only hint I can give is some kind of bisecting, but probably
you do not need such hint :-)
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2010-12-21 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 22:18 UBIFS not mounting on linux-omap 2.6.36 Charles Manning
2010-12-21 17:36 ` 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=1292952982.13362.21.camel@koala \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=manningc2@actrix.gen.nz \
/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).