linux-kernel - Re: [PATCH] spelling fixes: arch/powerpc/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <17989.1446.330976.16221@cargo.ozlabs.ibm.com>
Date:	Sat, 12 May 2007 10:09:10 +1000
From:	Paul Mackerras <paulus@...ba.org>
To:	Simon Arlott <simon@...e.lp0.eu>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linuxppc-dev@...abs.org, trivial@...nel.org
Subject: Re: [PATCH] spelling fixes: arch/powerpc/

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/