From: Paul Mackerras <paulus@samba.org>
To: Simon Arlott <simon@fire.lp0.eu>
Cc: linuxppc-dev@ozlabs.org, trivial@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] spelling fixes: arch/powerpc/
Date: Sat, 12 May 2007 10:09:10 +1000 [thread overview]
Message-ID: <17989.1446.330976.16221@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <4644C734.3000303@simon.arlott.org.uk>
Simon Arlott writes:
> Spelling fixes in arch/powerpc/.
> - /* Retreive CPU related informations from the flat tree
> + /* Retreive CPU related information from the flat tree
^^
You missed one. :)
> - /* Clear the freeze bit, and reenable the interrupt.
> + /* Clear the freeze bit, and re-enable the interrupt.
reenable -> re-enable is a bit marginal, but OK.
> /* Ok, now let's get cracking. You may ask me why I just didn't match
> * the iic host from the iic OF node, but that way I'm still compatible
> - * with really really old old firmwares for which we don't have a node
> + * with really really old old firmware for which we don't have a node
I think "firmwares" here was meaning to imply there were more than one
instance or release of firmware which had the property described, and
your change loses that.
> - * differenciate them all and since that hack was there for a long
> + * differentiate them all and since that hack was there for a long
I haven't been too strict about the Franglais in the past, but OK. :)
Paul.
prev parent reply other threads:[~2007-05-12 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 19:42 [PATCH] spelling fixes: arch/powerpc/ Simon Arlott
2007-05-11 20:32 ` Geoff Levand
2007-05-12 0:09 ` Paul Mackerras [this message]
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=17989.1446.330976.16221@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=simon@fire.lp0.eu \
--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;
as well as URLs for NNTP newsgroup(s).