From: Nadav Amit <namit@vmware.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Xin Hao <xhao@linux.alibaba.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
X86 ML <x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] x86/mm/tlb: fix error word 'clleared' to 'cleared'
Date: Thu, 29 Sep 2022 22:58:45 +0000 [thread overview]
Message-ID: <FD6D2974-13DD-4FE6-B175-E0BBF5306BD8@vmware.com> (raw)
In-Reply-To: <651530a9-2dc1-c781-a1b5-1e712684f94d@infradead.org>
On Sep 29, 2022, at 2:36 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
> ⚠ External Email
>
> Hi--
>
> I would say let's fix the sentence grammar, but I don't know
> what "cleared set" means.
>
>
> On 9/29/22 02:10, Xin Hao wrote:
>> Just correct the wrong word 'clleared' to 'cleared'
>>
>> Signed-off-by: Xin Hao <xhao@linux.alibaba.com>
>> ---
>> arch/x86/include/asm/tlbflush.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/x86/include/asm/tlbflush.h b/arch/x86/include/asm/tlbflush.h
>> index cda3118f3b27..c80a15ef0cbc 100644
>> --- a/arch/x86/include/asm/tlbflush.h
>> +++ b/arch/x86/include/asm/tlbflush.h
>> @@ -291,7 +291,7 @@ static inline bool pte_flags_need_flush(unsigned long oldflags,
>> diff &= ~_PAGE_ACCESSED;
>>
>> /*
>> - * Did any of the 'flush_on_clear' flags was clleared set from between
>> + * Did any of the 'flush_on_clear' flags was cleared set from between
>
> It should be more like:
>
> * Were any of the 'flush_on_clear' flags changed between
>
> X86 people, does that make sense to you?
It’s not a test whether the flags are changed, but whether they are cleared.
Let’s see if we can make it clearer with shorter sentences. How about:
“Consider the ‘flush_on_clear’ flags that are set on ‘oldflags’; Flush if
any of these flags is cleared on ’newflags’”.
next prev parent reply other threads:[~2022-09-29 22:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 9:10 Xin Hao
2022-09-29 21:36 ` Randy Dunlap
2022-09-29 22:58 ` Nadav Amit [this message]
2022-09-29 23:44 ` 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=FD6D2974-13DD-4FE6-B175-E0BBF5306BD8@vmware.com \
--to=namit@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xhao@linux.alibaba.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
all inboxes | Powered by JetHome®