summaryrefslogtreecommitdiff
path: root/drivers/mtd/devices
diff options
context:
space:
mode:
authorFrederik Schwarzer <schwarzerf@gmail.com>2008-10-16 19:02:37 +0200
committerJiri Kosina <jkosina@suse.cz>2009-01-06 11:28:06 +0100
commit025dfdafe77f20b3890981a394774baab7b9c827 (patch)
treec4d514990d7a0673df5d32aa11fded95f9644ff0 /drivers/mtd/devices
parent0abb8b6a939b742f273edc68b64dba26c57331bc (diff)
downloadlinux-next-025dfdafe77f20b3890981a394774baab7b9c827.tar.gz
trivial: fix then -> than typos in comments and documentation
- (better, more, bigger ...) then -> (...) than Signed-off-by: Frederik Schwarzer <schwarzerf@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'drivers/mtd/devices')
-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