From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752615AbaGGBKV (ORCPT ); Sun, 6 Jul 2014 21:10:21 -0400 Received: from casper.infradead.org ([85.118.1.10]:47637 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752001AbaGGBKT (ORCPT ); Sun, 6 Jul 2014 21:10:19 -0400 Message-ID: <53B9F377.5070803@infradead.org> Date: Sun, 06 Jul 2014 18:10:15 -0700 From: Randy Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Masanari Iida , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH] Documentation: Fix typo in DocBook files References: <1404444245-21906-1-git-send-email-standby24x7@gmail.com> In-Reply-To: <1404444245-21906-1-git-send-email-standby24x7@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/03/2014 08:24 PM, Masanari Iida wrote: > This patch fixed spelling typo in various template files > within Documentation/Docbook. > > Signed-off-by: Masanari Iida Applied, thanks. > --- > Documentation/DocBook/gadget.tmpl | 2 +- > Documentation/DocBook/genericirq.tmpl | 4 ++-- > Documentation/DocBook/kernel-locking.tmpl | 2 +- > Documentation/DocBook/libata.tmpl | 6 +++--- > Documentation/DocBook/media_api.tmpl | 2 +- > Documentation/DocBook/regulator.tmpl | 2 +- > Documentation/DocBook/uio-howto.tmpl | 4 ++-- > Documentation/DocBook/usb.tmpl | 2 +- > Documentation/DocBook/writing-an-alsa-driver.tmpl | 2 +- > 9 files changed, 13 insertions(+), 13 deletions(-) > > diff --git a/Documentation/DocBook/gadget.tmpl b/Documentation/DocBook/gadget.tmpl > index 4017f14..2c425d7 100644 > --- a/Documentation/DocBook/gadget.tmpl > +++ b/Documentation/DocBook/gadget.tmpl > @@ -708,7 +708,7 @@ hardware level details could be very different. > > Systems need specialized hardware support to implement OTG, > notably including a special Mini-AB jack > -and associated transciever to support Dual-Role > +and associated transceiver to support Dual-Role > operation: > they can act either as a host, using the standard > Linux-USB host side driver stack, > diff --git a/Documentation/DocBook/genericirq.tmpl b/Documentation/DocBook/genericirq.tmpl > index 46347f6..59fb5c0 100644 > --- a/Documentation/DocBook/genericirq.tmpl > +++ b/Documentation/DocBook/genericirq.tmpl > @@ -182,7 +182,7 @@ > > Each interrupt is described by an interrupt descriptor structure > irq_desc. The interrupt is referenced by an 'unsigned int' numeric > - value which selects the corresponding interrupt decription structure > + value which selects the corresponding interrupt description structure > in the descriptor structures array. > The descriptor structure contains status information and pointers > to the interrupt flow method and the interrupt chip structure > @@ -470,7 +470,7 @@ if (desc->irq_data.chip->irq_eoi) > > To avoid copies of identical implementations of IRQ chips the > core provides a configurable generic interrupt chip > - implementation. Developers should check carefuly whether the > + implementation. Developers should check carefully whether the > generic chip fits their needs before implementing the same > functionality slightly differently themselves. > > diff --git a/Documentation/DocBook/kernel-locking.tmpl b/Documentation/DocBook/kernel-locking.tmpl > index 19f2a5a..e584ee1 100644 > --- a/Documentation/DocBook/kernel-locking.tmpl > +++ b/Documentation/DocBook/kernel-locking.tmpl > @@ -1760,7 +1760,7 @@ as it would be on UP. > > > > -There is a furthur optimization possible here: remember our original > +There is a further optimization possible here: remember our original > cache code, where there were no reference counts and the caller simply > held the lock whenever using the object? This is still possible: if > you hold the lock, no one can delete the object, so you don't need to > diff --git a/Documentation/DocBook/libata.tmpl b/Documentation/DocBook/libata.tmpl > index deb71ba..d7fcdc5 100644 > --- a/Documentation/DocBook/libata.tmpl > +++ b/Documentation/DocBook/libata.tmpl > @@ -677,7 +677,7 @@ and other resources, etc. > > > > - ATA_QCFLAG_ACTIVE is clared from qc->flags. > + ATA_QCFLAG_ACTIVE is cleared from qc->flags. > > > > @@ -708,7 +708,7 @@ and other resources, etc. > > > > - qc->waiting is claread & completed (in that order). > + qc->waiting is cleared & completed (in that order). > > > > @@ -1163,7 +1163,7 @@ and other resources, etc. > > > Once sense data is acquired, this type of errors can be > - handled similary to other SCSI errors. Note that sense data > + handled similarly to other SCSI errors. Note that sense data > may indicate ATA bus error (e.g. Sense Key 04h HARDWARE ERROR > && ASC/ASCQ 47h/00h SCSI PARITY ERROR). In such > cases, the error should be considered as an ATA bus error and > diff --git a/Documentation/DocBook/media_api.tmpl b/Documentation/DocBook/media_api.tmpl > index 4decb46..03f9a1f 100644 > --- a/Documentation/DocBook/media_api.tmpl > +++ b/Documentation/DocBook/media_api.tmpl > @@ -68,7 +68,7 @@ > several digital tv standards. While it is called as DVB API, > in fact it covers several different video standards including > DVB-T, DVB-S, DVB-C and ATSC. The API is currently being updated > - to documment support also for DVB-S2, ISDB-T and ISDB-S. > + to document support also for DVB-S2, ISDB-T and ISDB-S. > The third part covers the Remote Controller API. > The fourth part covers the Media Controller API. > For additional information and for the latest development code, > diff --git a/Documentation/DocBook/regulator.tmpl b/Documentation/DocBook/regulator.tmpl > index 346e552..3b08a08 100644 > --- a/Documentation/DocBook/regulator.tmpl > +++ b/Documentation/DocBook/regulator.tmpl > @@ -155,7 +155,7 @@ > release regulators. Functions are > provided to enable > and disable the > - reguator and to get and set the runtime parameters of the > + regulator and to get and set the runtime parameters of the > regulator. > > > diff --git a/Documentation/DocBook/uio-howto.tmpl b/Documentation/DocBook/uio-howto.tmpl > index 9561815..bbe9c1f 100644 > --- a/Documentation/DocBook/uio-howto.tmpl > +++ b/Documentation/DocBook/uio-howto.tmpl > @@ -766,10 +766,10 @@ framework to set up sysfs files for this region. Simply leave it alone. > > The dynamic memory regions will be allocated when the UIO device file, > /dev/uioX is opened. > - Simiar to static memory resources, the memory region information for > + Similar to static memory resources, the memory region information for > dynamic regions is then visible via sysfs at > /sys/class/uio/uioX/maps/mapY/*. > - The dynmaic memory regions will be freed when the UIO device file is > + The dynamic memory regions will be freed when the UIO device file is > closed. When no processes are holding the device file open, the address > returned to userspace is ~0. > > diff --git a/Documentation/DocBook/usb.tmpl b/Documentation/DocBook/usb.tmpl > index 8d57c18..85fc0e2 100644 > --- a/Documentation/DocBook/usb.tmpl > +++ b/Documentation/DocBook/usb.tmpl > @@ -153,7 +153,7 @@ > > The Linux USB API supports synchronous calls for > control and bulk messages. > - It also supports asynchnous calls for all kinds of data transfer, > + It also supports asynchronous calls for all kinds of data transfer, > using request structures called "URBs" (USB Request Blocks). > > > diff --git a/Documentation/DocBook/writing-an-alsa-driver.tmpl b/Documentation/DocBook/writing-an-alsa-driver.tmpl > index d0056a4..6f639d9 100644 > --- a/Documentation/DocBook/writing-an-alsa-driver.tmpl > +++ b/Documentation/DocBook/writing-an-alsa-driver.tmpl > @@ -5696,7 +5696,7 @@ struct _snd_pcm_runtime { > suspending the PCM operations via > snd_pcm_suspend_all() or > snd_pcm_suspend(). It means that the PCM > - streams are already stoppped when the register snapshot is > + streams are already stopped when the register snapshot is > taken. But, remember that you don't have to restart the PCM > stream in the resume callback. It'll be restarted via > trigger call with SNDRV_PCM_TRIGGER_RESUME > -- ~Randy