TR: Notification d'envoi de fichier via http://dl.free.fr
Artem Bityutskiy
dedekind1 at gmail.com
Mon Sep 3 10:38:37 EDT 2012
On Mon, 2012-09-03 at 16:15 +0200, Fabien Comte wrote:
> Hello,
>
> 3.0, are you sure ?
> http://git.infradead.org/users/dedekind/ubifs-v3.0.git
> http://git.infradead.org/users/dedekind/ubifs-v3.5.git -> for 3.5 kernels, isn't it ?
Well, here is my logic.
You say that if you create an UBIFS image in v3.0, then try to mount it
in v3.4 - it fails, while it still mounts in 3.0. Correct?
Then, if you take the ubifs-v3.0.git tree, which contains v3.0 + all the
UBI/UBIFS patches, and try to mount your image, I expect it will also
fail.
If so, you will have the kernel which:
1. Works at the 'v3.0' point.
2. Fails at the 'HEAD' point.
Then you should be able to find out which commit is guilty using 'git
bisect'. Something like:
$ git bisect start
$ git bisect bad HEAD
$ git bisect good v3.0
If you manage to find the offending commit, fixing the issue should be
relatively easy, I think (and hope).
Makes sense?
--
Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20120903/725a1031/attachment-0001.sig>
More information about the linux-mtd
mailing list