From: David Woodhouse <dwmw2@infradead.org>
To: Alexander Larsson <alex@cendio.se>
Cc: mtd@infradead.org, "Sébastien Côté" <scote1@matrox.com>
Subject: Re: MTD CVS update: 'mtd/fs/jffs inode-v22.c Makefile inode.c'
Date: Fri, 16 Jun 2000 13:05:13 +0100 [thread overview]
Message-ID: <19871.961157113@cygnus.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.10.10006161357500.32189-100000@tammy.signum.se>
alex@cendio.se said:
>
> Btw. Do you want any help merging these?
Yes please.
I'm being confused by a more fundamental problem ATM.
include/linux/mtd/mtd.h includes <linux/module.h> because it needs to use
try_inc_mod_count().
Unfortunately, this means I get:
intrep.o(.modinfo+0x0): multiple definition of `__module_kernel_version'
jffs_fm.o(.modinfo+0x0): first defined here
inode-v22.o(.modinfo+0x0): multiple definition of `__module_kernel_version'
jffs_fm.o(.modinfo+0x0): first defined here
make[1]: *** [jffs.o] Error 1
Defining __NO_VERSION__ before including module.h, and then undefining it
afterwards, isn't right because that would mean that it doesn't get
processed correctly if the main file later includes module.h and _does_
want __module_kernel_version to be defined by it.
I suspect that for now I'm just going to cheat and define try_inc_mod_count
myself, but that's hardly ideal.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-06-16 12:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-16 11:13 MTD CVS update: 'mtd/fs/jffs inode-v22.c Makefile inode.c' David Woodhouse
2000-06-16 11:42 ` Alexander Larsson
2000-06-16 11:46 ` David Woodhouse
2000-06-16 11:49 ` Alexander Larsson
2000-06-16 12:31 ` David Woodhouse
2000-06-16 12:46 ` Alexander Larsson
2000-06-16 14:13 ` Alexander Larsson
2000-06-16 14:49 ` Sébastien Côté
2000-06-16 15:48 ` Sébastien Côté
2000-06-16 11:58 ` Alexander Larsson
2000-06-16 12:05 ` David Woodhouse [this message]
2000-06-16 12:17 ` Alexander Larsson
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=19871.961157113@cygnus.co.uk \
--to=dwmw2@infradead.org \
--cc=alex@cendio.se \
--cc=mtd@infradead.org \
--cc=scote1@matrox.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 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.