All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Stanislav Popov <s.popov@rsc.bg>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS ubimkvol issue and some others...
Date: Fri, 29 May 2009 18:53:16 +0300	[thread overview]
Message-ID: <1243612396.11172.119.camel@localhost.localdomain> (raw)
In-Reply-To: <4A1EC95A.1090806@rsc.bg>

On Thu, 2009-05-28 at 20:26 +0300, Stanislav Popov wrote:
> > How? It is not trivial. Did you use my old 2.6.21 backport tree?
> >   
> Yes, I ported it with the backport patch.

What you mean by "the backport patch"? Please, start from my old
back-port which you can find here:

http://git.infradead.org/users/dedekind/ubifs-v2.6.21.git

Make sure it works. Then you will have to back port important fixes
which are not there.

> >
> > Not sure. Probably related to your back-port. You'll have
> > to debug this yourself.
> >   
> Do you have any ideas how can I start debuging it ?

Well, inserting printk's to where it oopses, and investigate
why. Sorry, I'm not very interested to fix problem very old
kernels like 2.6.21. You are on your own here. But I suggest
you to start from taking UBIFS stuff from
git://git.infradead.org/users/dedekind/ubifs-v2.6.21.git

Vs the ubiformat failure - I'll investigate this. I think
I screwed up ubiformat in this commit:

http://git.infradead.org/mtd-utils.git?a=commit;h=32252f2b902d88f2991d260f2982b10b2016c33b

so you may try to git-reset to an earlier one so far. But
I'll investigate the issue later.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2009-05-29 15:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 12:44 UBIFS ubimkvol issue and some others Stanislav Popov
2009-05-28 15:16 ` Artem Bityutskiy
2009-05-28 17:26   ` Stanislav Popov
2009-05-29 15:53     ` Artem Bityutskiy [this message]
2009-06-02 12:44 ` Artem Bityutskiy
2009-06-02 13:35   ` Stanislav Popov
2009-06-02 13:40     ` Artem Bityutskiy
2009-06-02 14:03       ` Stanislav Popov
2009-06-02 14:09         ` Artem Bityutskiy

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=1243612396.11172.119.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=s.popov@rsc.bg \
    /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.