From: Fabrice Gautier <gautier@email.enst.fr>
To: David Woodhouse <dwmw2@infradead.org>
Cc: mtd@infradead.org
Subject: [PATCH] Makefiles + vmax301 (was Re: MTD CVS and Official Kernel Tree )
Date: Thu, 19 Apr 2001 22:11:19 +0200 [thread overview]
Message-ID: <20010419220359.0A46.GAUTIER@email.enst.fr> (raw)
In-Reply-To: <5889.987697556@redhat.com>
On Thu, 19 Apr 2001 17:25:56 +0100
David Woodhouse <dwmw2@infradead.org> wrote:
>
> gautier@email.enst.fr said:
> > Am I right when I assume that the mtd cvs tree can be applied to a 2.4
> > kernel tree by coppying directories like this?
>
> > mtd/drivers/mtd -------> linux/drivers/mtd
> > mtd/fs ----------------> linux/fs
> > mtd/include -----------> linux/include
>
> Yep. Assuming I got the Makefiles right. Which is unlikely.
The following patch make them good (for me), plus there is another patch
for an include problem in vmax301.c. (it's a "works for me" patch)
The problems were:
1/ target for nftl.o before global Rules
2/ $TOPDIR instead of $(TOPDIR) in some Makefiles
3/ mixmem.c has disapeared from CVS.
Index: drivers/mtd/Makefile
===================================================================
RCS file: /home/cvs/mtd/drivers/mtd/Makefile,v
retrieving revision 1.55
diff -u -r1.55 Makefile
--- drivers/mtd/Makefile 2001/04/18 21:09:29 1.55
+++ drivers/mtd/Makefile 2001/04/19 20:01:24
@@ -62,7 +62,8 @@
nftl-objs := nftlcore.o nftlmount.o
+include $(TOPDIR)/Rules.make
+
nftl.o: $(nftl-objs)
$(LD) -r -o $@ $(nftl-objs)
-include $(TOPDIR)/Rules.make
Index: drivers/mtd/chips/Makefile
===================================================================
RCS file: /home/cvs/mtd/drivers/mtd/chips/Makefile,v
retrieving revision 1.1
diff -u -r1.1 Makefile
--- drivers/mtd/chips/Makefile 2001/04/18 21:09:28 1.1
+++ drivers/mtd/chips/Makefile 2001/04/19 20:01:24
@@ -21,4 +21,4 @@
obj-$(CONFIG_MTD_ROM) += map_rom.o
obj-$(CONFIG_MTD_SHARP) += sharp.o
-include $TOPDIR/Rules.make
+include $(TOPDIR)/Rules.make
Index: drivers/mtd/devices/Makefile
===================================================================
RCS file: /home/cvs/mtd/drivers/mtd/devices/Makefile,v
retrieving revision 1.1
diff -u -r1.1 Makefile
--- drivers/mtd/devices/Makefile 2001/04/18 21:09:29 1.1
+++ drivers/mtd/devices/Makefile 2001/04/19 20:01:24
@@ -20,4 +20,4 @@
obj-$(CONFIG_MTD_PMC551) += pmc551.o
obj-$(CONFIG_MTD_MTDRAM) += mtdram.o
-include $TOPDIR/Rules.make
+include $(TOPDIR)/Rules.make
Index: drivers/mtd/maps/Makefile
===================================================================
RCS file: /home/cvs/mtd/drivers/mtd/maps/Makefile,v
retrieving revision 1.1
diff -u -r1.1 Makefile
--- drivers/mtd/maps/Makefile 2001/04/18 21:09:29 1.1
+++ drivers/mtd/maps/Makefile 2001/04/19 20:01:24
@@ -12,7 +12,6 @@
obj-$(CONFIG_MTD_DC21285) += dc21285.o
obj-$(CONFIG_MTD_ELAN_104NC) += elan-104nc.o
obj-$(CONFIG_MTD_IQ80310) += iq80310.o
-obj-$(CONFIG_MTD_MIXMEM) += mixmem.o
obj-$(CONFIG_MTD_NORA) += nora.o
obj-$(CONFIG_MTD_OCTAGON) += octagon-5066.o
obj-$(CONFIG_MTD_PHYSMAP) += physmap.o
@@ -24,4 +23,4 @@
obj-$(CONFIG_MTD_SUN_UFLASH) += sun_uflash.o
obj-$(CONFIG_MTD_VMAX) += vmax301.o
-include $TOPDIR/Rules.make
+include $(TOPDIR)/Rules.make
Index: drivers/mtd/nand/Makefile
===================================================================
RCS file: /home/cvs/mtd/drivers/mtd/nand/Makefile,v
retrieving revision 1.1
diff -u -r1.1 Makefile
--- drivers/mtd/nand/Makefile 2001/04/18 21:09:29 1.1
+++ drivers/mtd/nand/Makefile 2001/04/19 20:01:25
@@ -9,4 +9,4 @@
obj-$(CONFIG_MTD_NAND_ECC) += nand_ecc.o
obj-$(CONFIG_MTD_NAND_SPIA) += spia.o
-include $TOPDIR/Rules.make
+include $(TOPDIR)/Rules.make
This one is for an include problem in vmax301.c
Index: drivers/mtd/maps/vmax301.c
===================================================================
RCS file: /home/cvs/mtd/drivers/mtd/maps/vmax301.c,v
retrieving revision 1.19
diff -u -r1.19 vmax301.c
--- drivers/mtd/maps/vmax301.c 2001/03/17 16:18:29 1.19
+++ drivers/mtd/maps/vmax301.c 2001/04/19 20:01:25
@@ -20,7 +20,7 @@
#include <linux/malloc.h>
#include <linux/ioport.h>
#include <linux/init.h>
-#include <asm/spinlock.h>
+#include <linux/spinlock.h>
#include <asm/io.h>
#include <linux/mtd/map.h>
--
Fabrice Gautier <gautier@email.enstfr>
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-04-19 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 16:18 MTD CVS and Official Kernel Tree Fabrice Gautier
2001-04-19 16:25 ` David Woodhouse
2001-04-19 20:11 ` Fabrice Gautier [this message]
2001-04-20 1:05 ` [PATCH] Makefiles + vmax301 (was Re: MTD CVS and Official Kernel Tree ) David Woodhouse
2001-04-19 20:35 ` MTD CVS and Official Kernel Tree David Schleef
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=20010419220359.0A46.GAUTIER@email.enst.fr \
--to=gautier@email.enst.fr \
--cc=dwmw2@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox