From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
x86@kernel.org, hpa@zytor.com, keescook@chromium.org,
jpoimboe@redhat.com, jroedel@suse.de, hjl.tools@gmail.com,
nivedita@alum.mit.edu, inglorion@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch: x86: kernel: Adjust the words to suit sentences in the file vmlinux.lds.S
Date: Tue, 9 Mar 2021 11:10:44 +0530 [thread overview]
Message-ID: <YEcKXEO2/oz4Y/S0@ArchLinux> (raw)
In-Reply-To: <5bed08e7-ce2b-438a-5ba1-37ee27078be8@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]
On 21:10 Mon 08 Mar 2021, Randy Dunlap wrote:
>On 3/8/21 7:41 PM, Bhaskar Chowdhury wrote:
>>
>>
>> s/percpu/per CPU/
>> s/baremetal/bare metal/
>>
>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>
>Yeah, "bare metal" is a little better than "baremetal".
>
>OTOH, "percpu" is a kernel construct's name. It doesn't have to
>be proper English IMHO. (2 cents worth)
>
My bad ....disregard...pls...will be careful ...
>> ---
>> arch/x86/kernel/vmlinux.lds.S | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/x86/kernel/vmlinux.lds.S b/arch/x86/kernel/vmlinux.lds.S
>> index efd9e9ea17f2..592a44ad13b1 100644
>> --- a/arch/x86/kernel/vmlinux.lds.S
>> +++ b/arch/x86/kernel/vmlinux.lds.S
>> @@ -217,7 +217,7 @@ SECTIONS
>>
>> #if defined(CONFIG_X86_64) && defined(CONFIG_SMP)
>> /*
>> - * percpu offsets are zero-based on SMP. PERCPU_VADDR() changes the
>> + * per CPU offsets are zero-based on SMP. PERCPU_VADDR() changes the
>> * output PHDR, so the next output section - .init.text - should
>> * start another segment - init.
>> */
>> @@ -262,7 +262,7 @@ SECTIONS
>> /*
>> * start address and size of operations which during runtime
>> * can be patched with virtualization friendly instructions or
>> - * baremetal native ones. Think page table operations.
>> + * bare metal native ones. Think page table operations.
>> * Details in paravirt_types.h
>> */
>> . = ALIGN(8);
>> --
>
>
>--
>~Randy
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-03-09 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 3:41 [PATCH] arch: x86: kernel: Adjust the words to suit sentences in the file vmlinux.lds.S Bhaskar Chowdhury
2021-03-09 5:10 ` Randy Dunlap
2021-03-09 5:40 ` 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=YEcKXEO2/oz4Y/S0@ArchLinux \
--to=unixbhaskar@gmail.com \
--cc=bp@alien8.de \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=inglorion@google.com \
--cc=jpoimboe@redhat.com \
--cc=jroedel@suse.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nivedita@alum.mit.edu \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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