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

Commit 53cb4726 authored by Matt LaPlante's avatar Matt LaPlante Committed by Adrian Bunk
Browse files

Fix typos in Documentation/: 'S' 



This patch fixes typos in various Documentation txts. The patch addresses
some words starting with the letter 'S'.

Signed-off-by: default avatarMatt LaPlante <kernel1@cyberdogtech.com>
Acked-by: default avatarAlan Cox <alan@redhat.com>
Acked-by: default avatarRandy Dunlap <rdunlap@xenotime.net>
Signed-off-by: default avatarAdrian Bunk <bunk@stusta.de>
parent d6bc8ac9

Documentation/RCU/whatisRCU.txt

+1 −1
Original line number Diff line number Diff line
@@ -582,7 +582,7 @@ The rcu_read_lock() and rcu_read_unlock() primitive read-acquire 
and release a global reader-writer lock.  The synchronize_rcu()

primitive write-acquires this same lock, then immediately releases

it.  This means that once synchronize_rcu() exits, all RCU read-side

critical sections that were in progress before synchonize_rcu() was

critical sections that were in progress before synchronize_rcu() was

called are guaranteed to have completed -- there is no way that

synchronize_rcu() would have been able to write-acquire the lock

otherwise.

Documentation/block/biodoc.txt

+2 −2
Original line number Diff line number Diff line
@@ -890,7 +890,7 @@ Aside: 


  Kvec i/o:



  Ben LaHaise's aio code uses a slighly different structure instead

  Ben LaHaise's aio code uses a slightly different structure instead

  of kiobufs, called a kvec_cb. This contains an array of <page, offset, len>

  tuples (very much like the networking code), together with a callback function

  and data pointer. This is embedded into a brw_cb structure when passed
@@ -988,7 +988,7 @@ elevator_exit_fn Allocate and free any elevator specific storage 
				for a queue.



4.2 Request flows seen by I/O schedulers

All requests seens by I/O schedulers strictly follow one of the following three

All requests seen by I/O schedulers strictly follow one of the following three

flows.



 set_req_fn ->

Documentation/cpu-freq/cpufreq-stats.txt

+4 −4
Original line number Diff line number Diff line 


     CPU frequency and voltage scaling statictics in the Linux(TM) kernel

     CPU frequency and voltage scaling statistics in the Linux(TM) kernel





             L i n u x    c p u f r e q - s t a t s   d r i v e r
@@ -18,8 +18,8 @@ Contents 
1. Introduction



cpufreq-stats is a driver that provices CPU frequency statistics for each CPU.

This statistics is provided in /sysfs as a bunch of read_only interfaces. This

interface (when configured) will appear in a seperate directory under cpufreq

These statistics are provided in /sysfs as a bunch of read_only interfaces. This

interface (when configured) will appear in a separate directory under cpufreq

in /sysfs (<sysfs root>/devices/system/cpu/cpuX/cpufreq/stats/) for each CPU.

Various statistics will form read_only files under this directory.
@@ -115,7 +115,7 @@ basic statistics which includes time_in_state and total_trans. 


"CPU frequency translation statistics details" (CONFIG_CPU_FREQ_STAT_DETAILS)

provides fine grained cpufreq stats by trans_table. The reason for having a

seperate config option for trans_table is:

separate config option for trans_table is:

- trans_table goes against the traditional /sysfs rule of one value per

  interface. It provides a whole bunch of value in a 2 dimensional matrix

  form.

Documentation/dvb/cards.txt

+1 −1
Original line number Diff line number Diff line
@@ -5,7 +5,7 @@ Hardware supported by the linuxtv.org DVB drivers 
  frontends (i.e. tuner / demodulator units) used, usually without

  changing the product name, revision number or specs. Some cards

  are also available in versions with different frontends for

  DVB-S/DVB-C/DVB-T. Thus the frontend drivers are listed seperately.

  DVB-S/DVB-C/DVB-T. Thus the frontend drivers are listed separately.



  Note 1: There is no guarantee that every frontend driver works

  out of the box with every card, because of different wiring.

Documentation/fb/sstfb.txt

+12 −12
Original line number Diff line number Diff line
@@ -137,22 +137,22 @@ Bugs 
	- The driver is 16 bpp only, 24/32 won't work.

	- The driver is not your_favorite_toy-safe. this includes SMP...

          [Actually from inspection it seems to be safe - Alan]

	- when using XFree86 FBdev (X over fbdev) you may see strange color

	- When using XFree86 FBdev (X over fbdev) you may see strange color

	patterns at the border of your windows (the pixels lose the lowest

	byte -> basicaly the blue component nd some of the green) . I'm unable

	byte -> basically the blue component and some of the green). I'm unable

	to reproduce this with XFree86-3.3, but one of the testers has this

	problem with XFree86-4. apparently recent Xfree86-4.x solve this

	problem with XFree86-4. Apparently recent Xfree86-4.x solve this

	problem.

	- I didn't really test changing the palette, so you may find some weird

	things when playing with that.

	- Sometimes the driver will not recognise the DAC, and the

        initialisation will fail. this is specificaly true for

	voodoo 2 boards , but it should be solved in recent versions. please

        initialisation will fail. This is specifically true for

	voodoo 2 boards, but it should be solved in recent versions. Please

	contact me.

	- the 24/32 is not likely to work anytime soon , knowing that the

	hardware does ... unusual thigs in 24/32 bpp

	- When used with anther video board, current limitations of linux

	console subsystem can cause some troubles, specificaly, you should

	- The 24/32 is not likely to work anytime soon, knowing that the

	hardware does ... unusual things in 24/32 bpp.

	- When used with another video board, current limitations of the linux

	console subsystem can cause some troubles, specifically, you should

	disable software scrollback, as it can oops badly ...



Todo