aboutsummaryrefslogtreecommitdiff
path: root/arch/cris/arch-v10/drivers/axisflashmap.c
diff options
context:
space:
mode:
authorAdam Buchbinder2016-02-23 15:30:07 -0800
committerJiri Kosina2016-04-18 12:45:53 +0200
commit014b38ec694ce3fd11cfedbdee75d1fdcb031839 (patch)
treef042c67edaf2aa565c42b41ab079f617959f0651 /arch/cris/arch-v10/drivers/axisflashmap.c
parent0398b95fe4b3c90fbabfb39b77e635ec863ac040 (diff)
cris: Fix misspellings in comments.
Signed-off-by: Adam Buchbinder <adam.buchbinder@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'arch/cris/arch-v10/drivers/axisflashmap.c')
-rw-r--r--arch/cris/arch-v10/drivers/axisflashmap.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/cris/arch-v10/drivers/axisflashmap.c b/arch/cris/arch-v10/drivers/axisflashmap.c
index a4bbdfd37bd8..60d57c590032 100644
--- a/arch/cris/arch-v10/drivers/axisflashmap.c
+++ b/arch/cris/arch-v10/drivers/axisflashmap.c
@@ -212,7 +212,7 @@ static struct mtd_info *probe_cs(struct map_info *map_cs)
/*
* Probe each chip select individually for flash chips. If there are chips on
* both cse0 and cse1, the mtd_info structs will be concatenated to one struct
- * so that MTD partitions can cross chip boundries.
+ * so that MTD partitions can cross chip boundaries.
*
* The only known restriction to how you can mount your chips is that each
* chip select must hold similar flash chips. But you need external hardware