GitHub-Mirror/Star64_linux
2
0
Fork 0
mirror of https://github.com/Fishwaldo/Star64_linux.git synced 2025-07-04 21:31:51 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

cris: Fix misspellings in comments.

Browse source 
Signed-off-by: Adam Buchbinder <adam.buchbinder@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
This commit is contained in:
Adam Buchbinder 2016-02-23 15:30:07 -08:00 • committed by Jiri Kosina
parent 0398b95fe4
commit 014b38ec69
5 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
arch/cris/arch-v10/drivers/axisflashmap.c
View file

@ -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 * 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 * 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 * 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 * chip select must hold similar flash chips. But you need external hardware

2
arch/cris/arch-v32/drivers/axisflashmap.c
View file

@ -246,7 +246,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 * 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 * 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 * 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 * chip select must hold similar flash chips. But you need external hardware

2
arch/cris/arch-v32/drivers/cryptocop.c
View file

@ -525,7 +525,7 @@ static int setup_cipher_iv_desc(struct cryptocop_tfrm_ctx *tc, struct cryptocop_
return 0; return 0;
} }
/* Map the ouput length of the transform to operation output starting on the inject index. */ /* Map the output length of the transform to operation output starting on the inject index. */
static int create_input_descriptors(struct cryptocop_operation *operation, struct cryptocop_tfrm_ctx *tc, struct cryptocop_dma_desc **id, int alloc_flag) static int create_input_descriptors(struct cryptocop_operation *operation, struct cryptocop_tfrm_ctx *tc, struct cryptocop_dma_desc **id, int alloc_flag)
{ {
int err = 0; int err = 0;

2
arch/cris/arch-v32/mach-a3/dram_init.S
View file

@ -11,7 +11,7 @@
*/ */
/* Just to be certain the config file is included, we include it here /* Just to be certain the config file is included, we include it here
* explicitely instead of depending on it being included in the file that * explicitly instead of depending on it being included in the file that
* uses this code. * uses this code.
*/ */

2
arch/cris/arch-v32/mach-fs/dram_init.S
View file

@ -11,7 +11,7 @@
*/ */
/* Just to be certain the config file is included, we include it here /* Just to be certain the config file is included, we include it here
* explicitely instead of depending on it being included in the file that * explicitly instead of depending on it being included in the file that
* uses this code. * uses this code.
*/ */