From: Rodrigo Moya <rodrigo@linuxave.net>
To: Trevor Woolven <trevw@zentropix.com>
Cc: David Woodhouse <David.Woodhouse@mvhi.com>,
Rodrigo Moya <rmoya@tsai.es>, MTD List <mtd@infradead.org>,
trevorw@zentropix.com
Subject: Re: no success
Date: Fri, 28 Apr 2000 14:16:54 +0200 [thread overview]
Message-ID: <39098136.72FA8BE1@linuxave.net> (raw)
In-Reply-To: 39080C3B.B6F3A58B@zentropix.com
> Hi,
>
> Apologies but I've been away for 10 days or so.
> It sounds to me as if the init routines have not been set-up correctly
> as Dave suggested.
>
> linux/init/main.c - do_basic_setup() calls init_mtd()
> mtd.c - init_mtd() calls the rest of the configured init routines.
>
> I can't remember if there's much screen output to see, there should be
> something. If in doubt, try enabling the DBG output, (recompile with
> -DZDBG).
>
> Hope this helps, if not get back to me with some more details
>
It was my fault, I had applied the patch, but in a different directory,
and my makefile wasn't copying the patched init/main.c file. Sorry.
But now, I'm compiling with this fixed, and I get undefined references
to register_mtd_notifier and unregister_mtd_notifier, which are not in
the source tree I've got here. I've even dropped today the directory and
checked out from CVS a fresh copy.
And these two functions are neither in the linux source tree.
Thanks for your help!
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-04-28 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-17 10:57 no success Rodrigo Moya
[not found] ` <14587.2027.787434.857298@jodie.local>
2000-04-17 12:53 ` Rodrigo Moya
2000-04-18 16:59 ` David Woodhouse
2000-04-27 9:45 ` Trevor Woolven
2000-04-28 12:16 ` Rodrigo Moya [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-11 8:43 Rodrigo Moya
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=39098136.72FA8BE1@linuxave.net \
--to=rodrigo@linuxave.net \
--cc=David.Woodhouse@mvhi.com \
--cc=mtd@infradead.org \
--cc=rmoya@tsai.es \
--cc=trevorw@zentropix.com \
--cc=trevw@zentropix.com \
/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