From: David Woodhouse <dwmw2@infradead.org>
To: Vipin Malik <Vipin.Malik@daniel.com>
Cc: mtd@infradead.org
Subject: Re: Unable to mount compressed root f/s because init_mtd() does n ot r egister block device!
Date: Thu, 22 Feb 2001 13:18:09 +0000 [thread overview]
Message-ID: <29886.982847889@redhat.com> (raw)
In-Reply-To: <30724FF712DFD2119E6200104B2448920119744C@mail1>
Vipin.Malik@daniel.com said:
> But isn't the same init calls method used to init the stuff in the
> 2.4.x series of kernels. So it's not just a 2.2.18/19 issue.
Yes, but it works in 2.4, and it doesn't in 2.2.18. So we might as well just
use the 2.2.17 method in 2.2.18 instead of a hacked-up version of the 2.4
method.
> Vipin P.S. Did you look at the 2nd patch to inode-v23.c that I sent
> yesterday (to fix the partial page write stuff)?
Yeah - looks good, thanks. Can you commit it?
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-02-22 13:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 13:11 Unable to mount compressed root f/s because init_mtd() does n ot r egister block device! Vipin Malik
2001-02-22 13:18 ` David Woodhouse [this message]
2001-02-22 19:22 ` Vipin Malik
2001-02-22 19:00 ` David Woodhouse
2001-02-22 20:18 ` Vipin Malik
2001-02-22 21:32 ` Vipin Malik
2001-02-22 21:55 ` David Woodhouse
2001-02-22 22:41 ` Unable to mount compressed root f/s because init_mtd() does not " Vipin Malik
2001-02-23 8:24 ` David Woodhouse
2001-02-23 18:02 ` Vipin Malik
2001-02-23 17:37 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-02-22 5:26 Unable to mount compressed root f/s because init_mtd() does n ot " Vipin Malik
2001-02-22 8:08 ` David Woodhouse
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=29886.982847889@redhat.com \
--to=dwmw2@infradead.org \
--cc=Vipin.Malik@daniel.com \
--cc=mtd@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.