From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
rdunlap@infradead.org
Subject: Re: [PATCH] IA64: Trivial spelling fixes
Date: Sat, 20 Mar 2021 19:22:17 +0000 [thread overview]
Message-ID: <YFZImRuNCpQvX5Fi@Gentoo> (raw)
In-Reply-To: <a3f98ec2-46e4-c7be-5e73-96c768a35bef@physik.fu-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 2361 bytes --]
On 20:01 Sat 20 Mar 2021, John Paul Adrian Glaubitz wrote:
>Hi Bhaskar!
>
>On 3/20/21 7:23 PM, Bhaskar Chowdhury wrote:
>>
>> s/seralize/serialize/ .....three different places
>>
>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>> ---
>> arch/ia64/kernel/pal.S | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/ia64/kernel/pal.S b/arch/ia64/kernel/pal.S
>> index d3e22c018b68..06d01a070aae 100644
>> --- a/arch/ia64/kernel/pal.S
>> +++ b/arch/ia64/kernel/pal.S
>> @@ -86,7 +86,7 @@ GLOBAL_ENTRY(ia64_pal_call_static)
>> mov ar.pfs = loc1
>> mov rp = loc0
>> ;;
>> - srlz.d // seralize restoration of psr.l
>> + srlz.d // serialize restoration of psr.l
>> br.ret.sptk.many b0
>> END(ia64_pal_call_static)
>> EXPORT_SYMBOL(ia64_pal_call_static)
>> @@ -194,7 +194,7 @@ GLOBAL_ENTRY(ia64_pal_call_phys_static)
>> mov rp = loc0
>> ;;
>> mov ar.rsc=loc4 // restore RSE configuration
>> - srlz.d // seralize restoration of psr.l
>> + srlz.d // serialize restoration of psr.l
>> br.ret.sptk.many b0
>> END(ia64_pal_call_phys_static)
>> EXPORT_SYMBOL(ia64_pal_call_phys_static)
>> @@ -252,7 +252,7 @@ GLOBAL_ENTRY(ia64_pal_call_phys_stacked)
>> mov rp = loc0
>> ;;
>> mov ar.rsc=loc4 // restore RSE configuration
>> - srlz.d // seralize restoration of psr.l
>> + srlz.d // serialize restoration of psr.l
>> br.ret.sptk.many b0
>> END(ia64_pal_call_phys_stacked)
>> EXPORT_SYMBOL(ia64_pal_call_phys_stacked)
>> --
>> 2.26.2
>
>Thanks for fixing this. Btw, we usually use all-lowercase letters for architecture
>names in the Linux kernel, so it should probably be "ia64: Trivial spelling fixes".
>
>And the easiest way to get those fixes into the kernel would be through Andrew Morton's
>tree.
>
I did send it to Andrew to pick up . And I took a cue from the earlier commit
messages for the architecture ...like this :
4d5a31977cc6 [IA64] reformat pal.S to fit in 80 columns, fix typos
c12fb1885787 [IA64] remove unused PAL_CALL_IC_OFF
acb15c85de57 [IA64] Do not assume output registers be reservered.
....so followed the conventions :)
>Adrian
>
>--
> .''`. John Paul Adrian Glaubitz
>: :' : Debian Developer - glaubitz@debian.org
>`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-03-20 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 18:35 [PATCH] IA64: Trivial spelling fixes Bhaskar Chowdhury
2021-03-20 19:01 ` John Paul Adrian Glaubitz
2021-03-20 19:22 ` Bhaskar Chowdhury [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=YFZImRuNCpQvX5Fi@Gentoo \
--to=unixbhaskar@gmail.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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