From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Michael Opdenacker <michael-lists@free-electrons.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH 2.6.18] [TRIVIAL] Spelling fixes in Documentation/DocBook
Date: Fri, 22 Sep 2006 17:34:33 +0100 [thread overview]
Message-ID: <1158942873.24572.20.camel@localhost.localdomain> (raw)
In-Reply-To: <200609212318.07418.michael-lists@free-electrons.com>
Ar Iau, 2006-09-21 am 23:18 +0200, ysgrifennodd Michael Opdenacker:
> -<para>There's an <emphasis>ethernet</emphasis> gadget
> +<para>There's an <emphasis>Ethernet</emphasis> gadget
NAK, Ethernet is/was indeed a proper noun but it has become generic
> -and associated transciever to support <emphasis>Dual-Role</emphasis>
> +and associated transceiver to support <emphasis>Dual-Role</emphasis>
ACK
> - value which selects the corresponding interrupt decription structure
> + value which selects the corresponding interrupt description structure
ACK
> interrupt hardware and was therefore reimplemented with split
> - functionality for egde/level/simple/percpu interrupts. This is not
> + functionality for edge/level/simple/percpu interrupts. This is not
ACK - also per-cpu with hyphens ?
> - <title>The Linux Journalling API</title>
> + <title>The Linux Journaling API</title>
NAK. See previous multiple discussions.
> The preferred method of initializing structures is to use
> - designated initialisers, as defined by ISO C99, eg:
> + designated initializers, as defined by ISO C99, eg:
NAK. Policy is to keep existing language usage not Americanize nor
Anglicize.
> -you hold the lock, noone can delete the object, so you don't need to
> +you hold the lock, no one can delete the object, so you don't need to
ACK
> - support second drives on a port (such as SATA contollers) will
> + support second drives on a port (such as SATA controllers) will
> use ata_noop_dev_select().
ACK
> - Higher-level hooks, these two hooks can potentially supercede
> + Higher-level hooks, these two hooks can potentially supersede
NAK - Supercede is correct
> - ATA_QCFLAG_ACTIVE is clared from qc->flags.
> + ATA_QCFLAG_ACTIVE is cleared from qc->flags.
ACK
> - requirement during issuing or excution any ATA/ATAPI command.
> + requirement during issuing or executing any ATA/ATAPI command.
NAK. Please check changes before submission
> </para>
>
> <itemizedlist>
> @@ -951,7 +951,7 @@ and other resources, etc.
>
> <listitem>
> <para>
> - !BSY && ERR after CDB tranfer starts but before the
> + !BSY && ERR after CDB transfer starts but before the
ACK
> last byte of CDB is transferred. ATA/ATAPI standard states
...
Please also submit each set of changes separately
next prev parent reply other threads:[~2006-09-22 16:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 21:18 [PATCH 2.6.18] [TRIVIAL] Spelling fixes in Documentation/DocBook Michael Opdenacker
2006-09-21 22:07 ` Randy.Dunlap
2006-09-23 18:55 ` Michael Opdenacker
2006-09-22 16:34 ` Alan Cox [this message]
2006-09-22 16:36 ` Randy.Dunlap
2006-09-22 19:10 ` Alan Cox
2006-09-23 19:07 ` Michael Opdenacker
2006-09-23 21:02 ` Alan Cox
2006-09-23 9:51 ` David Woodhouse
2006-09-23 17:04 ` Randy Dunlap
2006-09-23 18:31 ` Lee Revell
2006-09-23 18:33 ` David Woodhouse
2006-09-23 18:47 ` Lee Revell
2006-09-23 19:32 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1158942873.24572.20.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=michael-lists@free-electrons.com \
--cc=trivial@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox