summaryrefslogtreecommitdiff
path: root/drivers/mtd/devices/pmc551.c
diff options
context:
space:
mode:
authorStephen Rothwell <sfr@canb.auug.org.au>2009-01-05 16:41:41 +1100
committerStephen Rothwell <sfr@canb.auug.org.au>2009-01-05 16:41:41 +1100
commitb26c5f8135905f527c114244d7341cbd36a950fc (patch)
tree895b7343ff40ca8965ff5d52275755a281d02793 /drivers/mtd/devices/pmc551.c
parentd1d8cf362a426f2d1e49b66c390a5229767ec109 (diff)
parent3fe5fcb24c5d5f3ec7f87ea910ed01ed68205188 (diff)
Merge commit 'trivial/for-next'
Diffstat (limited to 'drivers/mtd/devices/pmc551.c')
-rw-r--r--drivers/mtd/devices/pmc551.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/mtd/devices/pmc551.c b/drivers/mtd/devices/pmc551.c
index d38bca64bb15..d2fd550f7e09 100644
--- a/drivers/mtd/devices/pmc551.c
+++ b/drivers/mtd/devices/pmc551.c
@@ -34,7 +34,7 @@
* aperture size, not the dram size, and the V370PDC supplies no
* other method for memory size discovery. This problem is
* mostly only relevant when compiled as a module, as the
- * unloading of the module with an aperture size smaller then
+ * unloading of the module with an aperture size smaller than
* the ram will cause the driver to detect the onboard memory
* size to be equal to the aperture size when the module is
* reloaded. Soooo, to help, the module supports an msize