mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-29 03:01:39 -04:00
Fix typos in /Documentation : 'T''
This patch fixes typos in various Documentation txts. The patch addresses some +words starting with the letter 'T'. Signed-off-by: Matt LaPlante <[email protected]> Acked-by: Randy Dunlap <[email protected]> Signed-off-by: Adrian Bunk <[email protected]>
This commit is contained in:
parent
98c4f0c336
commit
fa00e7e152
22 changed files with 35 additions and 35 deletions
|
|
@ -127,7 +127,7 @@ The following information is available in this file:
|
|||
- Correct a reference to free'ed memory during controller
|
||||
shutdown.
|
||||
- Reset the bus on an SE->LVD change. This is required
|
||||
to reset our transcievers.
|
||||
to reset our transceivers.
|
||||
|
||||
1.3.5 (March 24th, 2003)
|
||||
- Fix a few register window mode bugs.
|
||||
|
|
|
|||
|
|
@ -436,7 +436,7 @@ linux-1.1.x and fairly stable since linux-1.2.x, and are also in FreeBSD
|
|||
the commas to periods, insmod won't interpret this as more than one
|
||||
string and write junk into our binary image. I consider it a bug in
|
||||
the insmod program that even if you wrap your string in quotes (quotes
|
||||
that pass the shell mind you and that insmod sees) it still treates
|
||||
that pass the shell mind you and that insmod sees) it still treats
|
||||
a comma inside of those quotes as starting a new variable, resulting
|
||||
in memory scribbles if you don't switch the commas to periods.
|
||||
|
||||
|
|
|
|||
|
|
@ -920,7 +920,7 @@
|
|||
completed in such a way, that they are now completely conform to the
|
||||
demands in the technical description of IBM. Main candidates were the
|
||||
DEVICE_INQUIRY, REQUEST_SENSE and DEVICE_CAPACITY commands. They must
|
||||
be tranferred by bypassing the internal command buffer of the adapter
|
||||
be transferred by bypassing the internal command buffer of the adapter
|
||||
or else the response can be a random result. GET_POS_INFO would be more
|
||||
safe in usage, if one could use the SUPRESS_EXCEPTION_SHORT, but this
|
||||
is not allowed by the technical references of IBM. (Sorry, folks, the
|
||||
|
|
|
|||
|
|
@ -393,7 +393,7 @@ struct sas_task {
|
|||
task_proto -- _one_ of enum sas_proto
|
||||
scatter -- pointer to scatter gather list array
|
||||
num_scatter -- number of elements in scatter
|
||||
total_xfer_len -- total number of bytes expected to be transfered
|
||||
total_xfer_len -- total number of bytes expected to be transferred
|
||||
data_dir -- PCI_DMA_...
|
||||
task_done -- callback when the task has finished execution
|
||||
};
|
||||
|
|
|
|||
|
|
@ -261,7 +261,7 @@ pairs are separated with a comma (no spaces allowed). A colon can be
|
|||
used instead of the equal mark. The definition is prepended by the
|
||||
string st=. Here is an example:
|
||||
|
||||
st=buffer_kbs:64,write_threhold_kbs:60
|
||||
st=buffer_kbs:64,write_threshold_kbs:60
|
||||
|
||||
The following syntax used by the old kernel versions is also supported:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue