public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Fabien Comte <fabien.comte@ercogener.com>
Cc: 'linux-mtd' <linux-mtd@lists.infradead.org>
Subject: RE: TR: Notification d'envoi de fichier via http://dl.free.fr
Date: Mon, 03 Sep 2012 17:38:37 +0300	[thread overview]
Message-ID: <1346683117.3061.61.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <001d01cd89de$84659fd0$8d30df70$@ercogener.com>

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

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

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-09-03 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120831133153.764EC3495D9@dl.free.fr>
     [not found] ` <003d01cd877e$39b71020$ad253060$@ercogener.com>
2012-09-03 11:20   ` TR: Notification d'envoi de fichier via http://dl.free.fr Artem Bityutskiy
2012-09-03 11:54     ` Artem Bityutskiy
2012-09-03 14:15       ` Fabien Comte
2012-09-03 14:38         ` 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=1346683117.3061.61.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=fabien.comte@ercogener.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox