All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vipin Malik <vmalik@danielind.com>
To: Der Herr Hofrat <der.herr@hofr.at>
Cc: mtd@infradead.org
Subject: Re: inter_module borken in 2.2.18 ?
Date: Mon, 12 Feb 2001 10:01:28 -0600	[thread overview]
Message-ID: <3A8808D7.427B34CB@danielind.com> (raw)
In-Reply-To: 200102111803.f1BI3t616320@kanga.hofr.at

I had the same problems with the 2.2 series of kernels. Modules DO NOT WORK (at
least did not for me).
I also could not find a intermodule patch for the 2.2.18 kernel.

I just moved on to 2.4.1 where things seems to compile ok (as modules- which is
what I wanted to do while
I was testing stuff).

There was one other issue:
in nftl.c (ver 1.66) line 624, there seems to be a typo. The define
MTD_DEBUG_LEVEL_1 should really be MTD_DEBUG_LEVEL1

When I made the change in my local copy of the file, it compiled ok (and seems
to work).

There were some other issues that I encountered while testing (with DOC2000),
that I'll detail in a later e-mail.

***
David Woodhouse,

I'm working with Both CFI raw flash (with jffs) and DOC2000 (w/ ext2 and if
possible jffs). Is someone writing
a HOWTO? I am willing to start one (with a FAQ) (and maintain it for a while)
if you guys will put it on the site (and/or CVS).

Vipin Malik

Sr. Design Engr.
Daniel Industries
Houston, TX.




Der Herr Hofrat wrote:

> Hi !
>
>  looks to me like inter_module is borken in 2.2.18 in include/linux/list.h .
>  anybody have it working with 2.2.18 ?
>
> hofrat
>
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

      reply	other threads:[~2001-02-12 15:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-11 18:03 inter_module borken in 2.2.18 ? Der Herr Hofrat
2001-02-12 16:01 ` Vipin Malik [this message]

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=3A8808D7.427B34CB@danielind.com \
    --to=vmalik@danielind.com \
    --cc=der.herr@hofr.at \
    --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.