From: David Woodhouse <dwmw2@infradead.org>
To: Konstantin Kletschke <lists@ku-gbr.de>
Cc: akpm@osdl.org, linux-mtd@lists.infradead.org
Subject: Re: jffs2 Oops on 2.6.10-rc1-mm5
Date: Wed, 17 Nov 2004 09:22:04 +0000 [thread overview]
Message-ID: <1100683325.9201.45.camel@localhost.localdomain> (raw)
In-Reply-To: <20041117092127.GB2201@synertronixx3>
On Wed, 2004-11-17 at 10:21 +0100, Konstantin Kletschke wrote:
> Am 2004-11-17 09:07 +0000 schrieb Artem B. Bityuckiy:
>
> > I don't know what version of MTD is in you kernel, I would advice you to
> > try the lastest MTD snapshot first.
>
> Me neither, simply the stuff which is in 2.6.10-rc1-mm5.
> Well I think Andrew Morton does not patch mtd stuff in there...
I believe he does when I've got stuff in bk://linux-mtd.bkbits.net/mtd-2.6
for him to put there. Which means there'll probably be MTD stuff in his
next offering, since Linus only took the 'strictly bugfixes only' tree
out of the two I offered him last night.
> I wonder, how to put the files from latest mtd snapshot into this
> kernel, simply copying files over?
Check the MTD code out from CVS and use the 'patchin.sh' script from the
patches/ directory.
--
dwmw2
next prev parent reply other threads:[~2004-11-17 9:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 8:55 jffs2 Oops on 2.6.10-rc1-mm5 Konstantin Kletschke
2004-11-17 9:04 ` Artem B. Bityuckiy
2004-11-17 9:18 ` Konstantin Kletschke
2004-11-17 9:26 ` Artem B. Bityuckiy
2004-11-17 9:07 ` Artem B. Bityuckiy
2004-11-17 9:21 ` Konstantin Kletschke
2004-11-17 9:22 ` David Woodhouse [this message]
2004-11-17 9:30 ` Andrew Morton
2004-11-17 9:24 ` Artem B. Bityuckiy
2004-11-17 9:46 ` Konstantin Kletschke
-- strict thread matches above, loose matches on Subject: below --
2004-11-16 12:44 Konstantin Kletschke
2004-11-16 13:00 ` Artem B. Bityuckiy
2004-11-16 13:16 ` Konstantin Kletschke
2004-11-16 16:42 ` Artem B. Bityuckiy
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=1100683325.9201.45.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-mtd@lists.infradead.org \
--cc=lists@ku-gbr.de \
/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