mtd/drivers/mtd/devices ms02-nv.c,1.5,1.6 ms02-nv.h,1.2,1.3

[David Woodhouse]

Update of /home/cvs/mtd/drivers/mtd/devices
In directory phoenix.infradead.org:/tmp/cvs-serv11614/drivers/mtd/devices

Modified Files:
	ms02-nv.c ms02-nv.h 
Log Message:
s/MB/MiB/g


Index: ms02-nv.c
===================================================================
RCS file: /home/cvs/mtd/drivers/mtd/devices/ms02-nv.c,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- ms02-nv.c	19 Aug 2003 09:24:35 -0000	1.5
+++ ms02-nv.c	19 Aug 2003 09:25:36 -0000	1.6
@@ -38,9 +38,9 @@
 
 /*
  * Addresses we probe for an MS02-NV at.  Modules may be located
- * at any 8MB boundary within a 0MB up to 112MB range or at any 32MB
- * boundary within a 0MB up to 448MB range.  We don't support a module
- * at 0MB, though.
+ * at any 8MiB boundary within a 0MiB up to 112MiB range or at any 32MiB
+ * boundary within a 0MiB up to 448MiB range.  We don't support a module
+ * at 0MiB, though.
  */
 static ulong ms02nv_addrs[] __initdata = {
 	0x07000000, 0x06800000, 0x06000000, 0x05800000, 0x05000000,
@@ -130,7 +130,7 @@
 
 	int ret = -ENODEV;
 
-	/* The module decodes 8MB of address space. */
+	/* The module decodes 8MiB of address space. */
 	mod_res = kmalloc(sizeof(*mod_res), GFP_KERNEL);
 	if (!mod_res)
 		return -ENOMEM;
@@ -233,7 +233,7 @@
 		goto err_out_csr_res;
 	}
 
-	printk(KERN_INFO "mtd%d: %s at 0x%08lx, size %uMB.\n",
+	printk(KERN_INFO "mtd%d: %s at 0x%08lx, size %uMiB.\n",
 		mtd->index, ms02nv_name, addr, size >> 20);
 
 	mp->next = root_ms02nv_mtd;

Index: ms02-nv.h
===================================================================
RCS file: /home/cvs/mtd/drivers/mtd/devices/ms02-nv.h,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ms02-nv.h	19 Aug 2003 09:24:35 -0000	1.2
+++ ms02-nv.h	19 Aug 2003 09:25:36 -0000	1.3
@@ -41,8 +41,8 @@
  * The diagnostic area defines two status words to be read by an
  * operating system, a magic ID to distinguish a MS02-NV board from
  * anything else and a status information providing results of tests
- * as well as the size of SRAM available, which can be 1MB or 2MB
- * (that's what the firmware handles; no idea if 2MB modules ever
+ * as well as the size of SRAM available, which can be 1MiB or 2MiB
+ * (that's what the firmware handles; no idea if 2MiB modules ever
  * existed).
  *
  * The firmware only handles the MS02-NV board if installed in the