From: Richard Purdie <rpurdie@rpsys.net>
To: Jonathan McDowell <noodles@earth.li>
Cc: linux-mtd@lists.infradead.org
Subject: Re: 2.6.18-rc4 jffs2 problems
Date: Tue, 15 Aug 2006 23:29:11 +0100 [thread overview]
Message-ID: <1155680951.5542.19.camel@localhost.localdomain> (raw)
In-Reply-To: <20060810060409.GH27094@earth.li>
On Thu, 2006-08-10 at 07:04 +0100, Jonathan McDowell wrote:
> A "git bisect" is flagging up 8593fbc68b0df1168995de76d1af38eb62fd6b62
> as the problem commit:
>
> commit 8593fbc68b0df1168995de76d1af38eb62fd6b62
> Author: Thomas Gleixner <tglx@cruncher.tec.linutronix.de>
> Date: Mon May 29 03:26:58 2006 +0200
>
> [MTD] Rework the out of band handling completely
I found time to do some testing myself and can confirm this is the
problem patch for sharpsl as well. I don't see the problem with recent
git kernels if I apply:
http://www.rpsys.net/openzaurus/patches/mtd_revert_oob-r0.patch
which is a hack reverting the above change (only on the bits of the
kernel which sharpsl needs). I'll see if I can trim the diff down and
find the problem...
Richard
next prev parent reply other threads:[~2006-08-15 22:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 18:41 2.6.18-rc4 jffs2 problems Richard Purdie
2006-08-08 6:40 ` Andrew Morton
2006-08-08 7:15 ` Artem B. Bityutskiy
2006-08-09 9:34 ` Jonathan McDowell
2006-08-10 6:04 ` Jonathan McDowell
2006-08-10 9:29 ` Artem B. Bityutskiy
2006-08-15 22:29 ` Richard Purdie [this message]
2006-08-17 22:09 ` Richard Purdie
2006-08-20 1:34 ` Josh Boyer
2006-08-20 1:34 ` Josh Boyer
2006-08-21 1:35 ` Greg KH
2006-08-21 1:35 ` Greg KH
2006-08-22 14:12 ` David Woodhouse
2006-08-22 14:12 ` David Woodhouse
2006-08-22 14:39 ` Josh Boyer
2006-08-22 14:39 ` Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2006-08-08 8:07 Koeller, T.
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=1155680951.5542.19.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=linux-mtd@lists.infradead.org \
--cc=noodles@earth.li \
/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.