From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"trivial@kernel.org" <trivial@kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"socketcan-core@lists.berlios.de"
<socketcan-core@lists.berlios.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC 1/6]Fix typo "recieve" in various parts of the kernel.
Date: Fri, 08 Apr 2011 08:06:23 -0700 [thread overview]
Message-ID: <4D9F246F.2030305@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1104080909040.5186@lnxricardw.se.axis.com>
On 04/08/2011 12:14 AM, Ricard Wanderlof wrote:
>
> On Fri, 8 Apr 2011, Justin P. Mattock wrote:
>
>> On 04/07/2011 01:05 PM, Uwe Kleine-König wrote:
>>> On Thu, Apr 07, 2011 at 09:09:22AM -0700, Justin P. Mattock wrote:
>>>> The patch below fixes some typos "recieve" in various parts of the
>>>> kernel.
>>>> Note: these below are in actual code rather than comments(excpet for
>>>> r852.c which
>>> s/excpet/except/
>>>
>>>> has a code fix, and comment).
>>>> compile tested as best as I can...
>>> I'm not a native speaker, but "as good as" sounds better in my ears.
>>>
>>> Best regards
>>> Uwe
>>>
>>
>> your right.. gcc and friends are the one's doing all the reall work:
>> "as good as *"
>
> I think Uwe was thinking of grammar rather than who was doing the actual
> work.
>
> Now that I've gone more or less off topic I may as well voice my opinion
> the 'as best as I can' sounds like a mixup of two constructs: either 'as
> best I can' (which is probably slightly unusual these days), or 'as well
> as I can'. 'I've done it as good as I can' is gramatically wrong (since
> 'good' is an adjective and 'well' is an adverb, and it is referring to
> 'how I did it' (or in the case above, 'how well I tested it'), but
> fairly common nevertheless, and given the large percentage of non-native
> speakers in the Linux community I wouldn't worry about it, the meaning
> is clear anyway.
>
> I'll shut up and go now. :-)
>
> /Ricard
well... pretty good explanation.
Justin P. Mattock
next prev parent reply other threads:[~2011-04-08 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 16:09 [RFC 1/6]Fix typo "recieve" in various parts of the kernel Justin P. Mattock
2011-04-07 20:05 ` Uwe Kleine-König
2011-04-07 23:35 ` Justin P. Mattock
2011-04-08 7:14 ` Ricard Wanderlof
2011-04-08 15:06 ` Justin P. Mattock [this message]
2011-04-07 20:32 ` Jesper Juhl
2011-04-07 20:43 ` Justin P. Mattock
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=4D9F246F.2030305@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ricard.wanderlof@axis.com \
--cc=socketcan-core@lists.berlios.de \
--cc=trivial@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).