From: David Woodhouse <dwmw2@infradead.org>
To: Robert Love <rml@tech9.net>
Cc: torvalds@transmeta.com, Keith Owens <kaos@ocs.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.14 errors on full build - Y
Date: Tue, 06 Nov 2001 14:56:31 +0000 [thread overview]
Message-ID: <26659.1005058591@redhat.com> (raw)
In-Reply-To: <1005024157.1506.2.camel@phantasy>
In-Reply-To: <1005024157.1506.2.camel@phantasy> <17526.1005022179@ocs3.intra.ocs.com.au>
rml@tech9.net said:
> Another simple fix...the multiple function declarations should be
> static. Even better, a lot of the duplication between the driver
> should be shared but that I shall leave as an exercises for the
> maintainer. Until then, Linus, please apply.
jedec.c is obsolete and will be going away just as soon as I'm sufficiently
convinced that jedec_probe.c and the unified flash driver backends are
actually working for all the hardware in question. You should never need to
have them both turned on at once.
Here's the fix, though, which also makes some other stuff static which
doesn't need to be exported.
Index: include/linux/mtd/jedec.h
===================================================================
RCS file: /home/cvs/mtd/include/linux/mtd/jedec.h,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- include/linux/mtd/jedec.h 2000/07/04 07:21:51 1.1
+++ include/linux/mtd/jedec.h 2001/11/06 14:37:36 1.2
@@ -7,7 +7,7 @@
*
* See the AMD flash databook for information on how to operate the interface.
*
- * $Id: jedec.h,v 1.1 2000/07/04 07:21:51 jgg Exp $
+ * $Id: jedec.h,v 1.2 2001/11/06 14:37:36 dwmw2 Exp $
*/
#ifndef __LINUX_MTD_JEDEC_H__
@@ -63,7 +63,5 @@
struct jedec_flash_chip chips[MAX_JEDEC_CHIPS];
};
-
-extern const struct JEDECTable *jedec_idtoinf(__u8 mfr,__u8 id);
#endif
Index: drivers/mtd/chips/jedec.c
===================================================================
RCS file: /home/cvs/mtd/drivers/mtd/chips/jedec.c,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- drivers/mtd/chips/jedec.c 2001/10/02 15:05:12 1.11
+++ drivers/mtd/chips/jedec.c 2001/11/06 14:37:35 1.12
@@ -11,7 +11,7 @@
* not going to guess how to send commands to them, plus I expect they will
* all speak CFI..
*
- * $Id: jedec.c,v 1.11 2001/10/02 15:05:12 dwmw2 Exp $
+ * $Id: jedec.c,v 1.12 2001/11/06 14:37:35 dwmw2 Exp $
*/
#include <linux/mtd/jedec.h>
@@ -42,6 +42,7 @@
{0xC2AD,"Macronix MX29F016",2*1024*1024,64*1024,MTD_CAP_NORFLASH},
{}};
+static const struct JEDECTable *jedec_idtoinf(__u8 mfr,__u8 id);
static void jedec_sync(struct mtd_info *mtd) {};
static int jedec_read(struct mtd_info *mtd, loff_t from, size_t len,
size_t *retlen, u_char *buf);
@@ -249,7 +250,7 @@
/* Take an array of JEDEC numbers that represent interleved flash chips
and process them. Check to make sure they are good JEDEC numbers, look
them up and then add them to the chip list */
-int handle_jedecs(struct map_info *map,__u8 *Mfg,__u8 *Id,unsigned Count,
+static int handle_jedecs(struct map_info *map,__u8 *Mfg,__u8 *Id,unsigned Count,
unsigned long base,struct jedec_private *priv)
{
unsigned I,J;
@@ -336,7 +337,7 @@
}
/* Lookup the chip information from the JEDEC ID table. */
-const struct JEDECTable *jedec_idtoinf(__u8 mfr,__u8 id)
+static const struct JEDECTable *jedec_idtoinf(__u8 mfr,__u8 id)
{
__u16 Id = (mfr << 8) | id;
unsigned long I = 0;
@@ -873,19 +874,19 @@
}
}
-int __init jedec_probe_init(void)
+int __init jedec_init(void)
{
register_mtd_chip_driver(&jedec_chipdrv);
return 0;
}
-static void __exit jedec_probe_exit(void)
+static void __exit jedec_exit(void)
{
unregister_mtd_chip_driver(&jedec_chipdrv);
}
-module_init(jedec_probe_init);
-module_exit(jedec_probe_exit);
+module_init(jedec_init);
+module_exit(jedec_exit);
MODULE_LICENSE("GPL");
MODULE_AUTHOR("Jason Gunthorpe <jgg@deltatee.com> et al.");
--
dwmw2
prev parent reply other threads:[~2001-11-06 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 4:49 2.4.14 errors on full build - Y Keith Owens
2001-11-06 5:16 ` [PATCH] " Robert Love
2001-11-06 5:22 ` Robert Love
2001-11-06 14:56 ` David Woodhouse [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=26659.1005058591@redhat.com \
--to=dwmw2@infradead.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=torvalds@transmeta.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.