All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: Re: Oops in 2.6.10-rc2
Date: Tue, 15 Feb 2005 16:02:32 +0100	[thread overview]
Message-ID: <20050215150231.GA831@synertronixx3> (raw)
In-Reply-To: <1108463611.26412.27.camel@sauron.oktetlabs.ru>

Am 2005-02-15 13:33 +0300 schrieb Artem B. Bityuckiy:

> IIRC, there were some NOR-related bug fixes. I would just see the
> revision of your nodemngmnt.c file and compare with the latest revision.
> I believe the distance is one or two commits. You may port them or just
> use the latest nodemngmnt.c - with high probability it will work well.

Ok, I will try that and fetch a new nodemgmnt.c tomorrow.
Now I am at my XIP construction set :(

Thanks for your help, Konsti

-- 
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E  A080 1E69 3FDA EF62 FCEF

  reply	other threads:[~2005-02-15 15:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14 14:36 Oops in 2.6.10-rc2 Konstantin Kletschke
2005-02-15 10:33 ` Artem B. Bityuckiy
2005-02-15 15:02   ` Konstantin Kletschke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-19 10:50 OOPS " Jim Nelson

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=20050215150231.GA831@synertronixx3 \
    --to=lists@ku-gbr.de \
    --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 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.