Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 3ad2f3fb authored by Daniel Mack's avatar Daniel Mack Committed by Jiri Kosina
Browse files

tree-wide: Assorted spelling fixes 



In particular, several occurances of funny versions of 'success',
'unknown', 'therefore', 'acknowledge', 'argument', 'achieve', 'address',
'beginning', 'desirable', 'separate' and 'necessary' are fixed.

Signed-off-by: default avatarDaniel Mack <daniel@caiaq.de>
Cc: Joe Perches <joe@perches.com>
Cc: Junio C Hamano <gitster@pobox.com>
Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
parent 1537a363

Documentation/DocBook/mtdnand.tmpl

+3 −3
Original line number Diff line number Diff line
@@ -488,7 +488,7 @@ static void board_select_chip (struct mtd_info *mtd, int chip) 
				The ECC bytes must be placed immidiately after the data

				bytes in order to make the syndrome generator work. This

				is contrary to the usual layout used by software ECC. The

				seperation of data and out of band area is not longer

				separation of data and out of band area is not longer

				possible. The nand driver code handles this layout and

				the remaining free bytes in the oob area are managed by 

				the autoplacement code. Provide a matching oob-layout
@@ -560,7 +560,7 @@ static void board_select_chip (struct mtd_info *mtd, int chip) 
				bad blocks. They have factory marked good blocks. The marker pattern

				is erased when the block is erased to be reused. So in case of

				powerloss before writing the pattern back to the chip this block 

				would be lost and added to the bad blocks. Therefor we scan the 

				would be lost and added to the bad blocks. Therefore we scan the 

				chip(s) when we detect them the first time for good blocks and 

				store this information in a bad block table before erasing any 

				of the blocks.
@@ -1094,7 +1094,7 @@ in this page</entry> 
		manufacturers specifications. This applies similar to the spare area. 

	</para>

	<para>

		Therefor NAND aware filesystems must either write in page size chunks

		Therefore NAND aware filesystems must either write in page size chunks

		or hold a writebuffer to collect smaller writes until they sum up to 

		pagesize. Available NAND aware filesystems: JFFS2, YAFFS. 		

	</para>

Documentation/DocBook/v4l/common.xml

+1 −1
Original line number Diff line number Diff line
@@ -1170,7 +1170,7 @@ frames per second. If less than this number of frames is to be 
captured or output, applications can request frame skipping or

duplicating on the driver side. This is especially useful when using

the &func-read; or &func-write;, which are not augmented by timestamps

or sequence counters, and to avoid unneccessary data copying.</para>

or sequence counters, and to avoid unnecessary data copying.</para>



    <para>Finally these ioctls can be used to determine the number of

buffers used internally by a driver in read/write mode. For

Documentation/DocBook/v4l/vidioc-g-parm.xml

+1 −1
Original line number Diff line number Diff line
@@ -55,7 +55,7 @@ captured or output, applications can request frame skipping or 
duplicating on the driver side. This is especially useful when using

the <function>read()</function> or <function>write()</function>, which

are not augmented by timestamps or sequence counters, and to avoid

unneccessary data copying.</para>

unnecessary data copying.</para>



    <para>Further these ioctls can be used to determine the number of

buffers used internally by a driver in read/write mode. For

Documentation/arm/Samsung-S3C24XX/CPUfreq.txt

+2 −2
Original line number Diff line number Diff line
@@ -14,8 +14,8 @@ Introduction 
 how the clocks are arranged. The first implementation used as single

 PLL to feed the ARM, memory and peripherals via a series of dividers

 and muxes and this is the implementation that is documented here. A

 newer version where there is a seperate PLL and clock divider for the

 ARM core is available as a seperate driver.

 newer version where there is a separate PLL and clock divider for the

 ARM core is available as a separate driver.





Layout

Documentation/hwmon/abituguru

+1 −1
Original line number Diff line number Diff line
@@ -30,7 +30,7 @@ Supported chips: 
	   bank1_types=1,1,0,0,0,0,0,2,0,0,0,0,2,0,0,1

	   You may also need to specify the fan_sensors option for these boards

	   fan_sensors=5

	2) There is a seperate abituguru3 driver for these motherboards,

	2) There is a separate abituguru3 driver for these motherboards,

	   the abituguru (without the 3 !) driver will not work on these

	   motherboards (and visa versa)!