From: Michael Ellerman <mpe@ellerman.id.au>
To: Randy Dunlap <rdunlap@infradead.org>,
Bhaskar Chowdhury <unixbhaskar@gmail.com>,
benh@kernel.crashing.org, paulus@samba.org,
akpm@linux-foundation.org, rppt@kernel.org, oss@buserror.net,
christophe.leroy@csgroup.eu, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: kernel: Trivial spelling fixes throughout the file head_fsl_booke.S
Date: Mon, 15 Mar 2021 13:48:25 +1100 [thread overview]
Message-ID: <87r1kh3zeu.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <f8dc3cbe-54f4-1da1-b14f-4735d28aad13@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> On 3/14/21 3:04 PM, Bhaskar Chowdhury wrote:
>>
>> Trivial spelling fixes throughout the file.
>>
>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>> ---
>> arch/powerpc/kernel/head_fsl_booke.S | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/powerpc/kernel/head_fsl_booke.S b/arch/powerpc/kernel/head_fsl_booke.S
>> index fdd4d274c245..c6fcfca0b0d7 100644
>> --- a/arch/powerpc/kernel/head_fsl_booke.S
>> +++ b/arch/powerpc/kernel/head_fsl_booke.S
>> @@ -403,7 +403,7 @@ interrupt_base:
>> EXCEPTION(0x2900, AP_UNAVAIL, AuxillaryProcessorUnavailable, \
>> unknown_exception, EXC_XFER_STD)
>>
>> - /* Decrementer Interrupt */
>> + /* Decremented Interrupt */
>
> No, the comment matches the macro (or whatever that is).
Right. I dropped this hunk. Please update your script or whatever to not
"correct" that spelling.
cheers
next prev parent reply other threads:[~2021-03-15 2:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 22:04 [PATCH] powerpc: kernel: Trivial spelling fixes throughout the file head_fsl_booke.S Bhaskar Chowdhury
2021-03-15 0:37 ` Randy Dunlap
2021-03-15 2:48 ` Michael Ellerman [this message]
2021-03-15 3:26 ` Bhaskar Chowdhury
2021-03-31 1:09 ` Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
2021-03-15 3:37 Bhaskar Chowdhury
2021-03-22 18:50 ` Randy Dunlap
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=87r1kh3zeu.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oss@buserror.net \
--cc=paulus@samba.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=unixbhaskar@gmail.com \
/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