+1 -1

Documentation/DocBook/gadget.tmpl

reviewed

··· 708 708 709 709 <para>Systems need specialized hardware support to implement OTG, 710 710 notably including a special <emphasis>Mini-AB</emphasis> jack 711 711 - and associated transciever to support <emphasis>Dual-Role</emphasis> 711 711 + and associated transceiver to support <emphasis>Dual-Role</emphasis> 712 712 operation: 713 713 they can act either as a host, using the standard 714 714 Linux-USB host side driver stack,

+2 -2

Documentation/DocBook/genericirq.tmpl

reviewed

··· 182 182 <para> 183 183 Each interrupt is described by an interrupt descriptor structure 184 184 irq_desc. The interrupt is referenced by an 'unsigned int' numeric 185 185 - value which selects the corresponding interrupt decription structure 185 185 + value which selects the corresponding interrupt description structure 186 186 in the descriptor structures array. 187 187 The descriptor structure contains status information and pointers 188 188 to the interrupt flow method and the interrupt chip structure ··· 470 470 <para> 471 471 To avoid copies of identical implementations of IRQ chips the 472 472 core provides a configurable generic interrupt chip 473 473 - implementation. Developers should check carefuly whether the 473 473 + implementation. Developers should check carefully whether the 474 474 generic chip fits their needs before implementing the same 475 475 functionality slightly differently themselves. 476 476 </para>

+1 -1

Documentation/DocBook/kernel-locking.tmpl

reviewed

··· 1760 1760 </para> 1761 1761 1762 1762 <para> 1763 1763 - There is a furthur optimization possible here: remember our original 1763 1763 + There is a further optimization possible here: remember our original 1764 1764 cache code, where there were no reference counts and the caller simply 1765 1765 held the lock whenever using the object? This is still possible: if 1766 1766 you hold the lock, no one can delete the object, so you don't need to

+3 -3

Documentation/DocBook/libata.tmpl

reviewed

··· 677 677 678 678 <listitem> 679 679 <para> 680 680 - ATA_QCFLAG_ACTIVE is clared from qc->flags. 680 680 + ATA_QCFLAG_ACTIVE is cleared from qc->flags. 681 681 </para> 682 682 </listitem> 683 683 ··· 708 708 709 709 <listitem> 710 710 <para> 711 711 - qc->waiting is claread &amp; completed (in that order). 711 711 + qc->waiting is cleared &amp; completed (in that order). 712 712 </para> 713 713 </listitem> 714 714 ··· 1163 1163 1164 1164 <para> 1165 1165 Once sense data is acquired, this type of errors can be 1166 1166 - handled similary to other SCSI errors. Note that sense data 1166 1166 + handled similarly to other SCSI errors. Note that sense data 1167 1167 may indicate ATA bus error (e.g. Sense Key 04h HARDWARE ERROR 1168 1168 &amp;&amp; ASC/ASCQ 47h/00h SCSI PARITY ERROR). In such 1169 1169 cases, the error should be considered as an ATA bus error and

+1 -1

Documentation/DocBook/media_api.tmpl

reviewed

··· 68 68 several digital tv standards. While it is called as DVB API, 69 69 in fact it covers several different video standards including 70 70 DVB-T, DVB-S, DVB-C and ATSC. The API is currently being updated 71 71 - to documment support also for DVB-S2, ISDB-T and ISDB-S.</para> 71 71 + to document support also for DVB-S2, ISDB-T and ISDB-S.</para> 72 72 <para>The third part covers the Remote Controller API.</para> 73 73 <para>The fourth part covers the Media Controller API.</para> 74 74 <para>For additional information and for the latest development code,

+1 -1

Documentation/DocBook/regulator.tmpl

reviewed

··· 155 155 release regulators. Functions are 156 156 provided to <link linkend='API-regulator-enable'>enable</link> 157 157 and <link linkend='API-regulator-disable'>disable</link> the 158 158 - reguator and to get and set the runtime parameters of the 158 158 + regulator and to get and set the runtime parameters of the 159 159 regulator. 160 160 </para> 161 161 <para>

+2 -2

Documentation/DocBook/uio-howto.tmpl

reviewed

··· 766 766 <para> 767 767 The dynamic memory regions will be allocated when the UIO device file, 768 768 <varname>/dev/uioX</varname> is opened. 769 769 - Simiar to static memory resources, the memory region information for 769 769 + Similar to static memory resources, the memory region information for 770 770 dynamic regions is then visible via sysfs at 771 771 <varname>/sys/class/uio/uioX/maps/mapY/*</varname>. 772 772 - The dynmaic memory regions will be freed when the UIO device file is 772 772 + The dynamic memory regions will be freed when the UIO device file is 773 773 closed. When no processes are holding the device file open, the address 774 774 returned to userspace is ~0. 775 775 </para>

+1 -1

Documentation/DocBook/usb.tmpl

reviewed

··· 153 153 154 154 <listitem><para>The Linux USB API supports synchronous calls for 155 155 control and bulk messages. 156 156 - It also supports asynchnous calls for all kinds of data transfer, 156 156 + It also supports asynchronous calls for all kinds of data transfer, 157 157 using request structures called "URBs" (USB Request Blocks). 158 158 </para></listitem> 159 159

+1 -1

Documentation/DocBook/writing-an-alsa-driver.tmpl

reviewed

··· 5696 5696 suspending the PCM operations via 5697 5697 <function>snd_pcm_suspend_all()</function> or 5698 5698 <function>snd_pcm_suspend()</function>. It means that the PCM 5699 5699 - streams are already stoppped when the register snapshot is 5699 5699 + streams are already stopped when the register snapshot is 5700 5700 taken. But, remember that you don't have to restart the PCM 5701 5701 stream in the resume callback. It'll be restarted via 5702 5702 trigger call with <constant>SNDRV_PCM_TRIGGER_RESUME</constant>