From: Peter Zijlstra <peterz@infradead.org>
To: Xin Hao <xhao@linux.alibaba.com>
Cc: namit@vmware.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/mm/tlb: fix error word 'clleared' to 'cleared'
Date: Thu, 29 Sep 2022 10:52:57 +0200 [thread overview]
Message-ID: <YzVc6UwLSwkG7jKX@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20220928151109.19364-1-xhao@linux.alibaba.com>
On Wed, Sep 28, 2022 at 11:11:09PM +0800, Xin Hao wrote:
> Just correct the wrong word 'clleared' to 'cleared'
>
> Fixes: c9fe66560bf2 ("mm/mprotect: do not flush when not required architecturally")
Please, don't ever use Fixes on a comment.
next prev parent reply other threads:[~2022-09-29 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 15:11 [PATCH] x86/mm/tlb: fix error word 'clleared' to 'cleared' Xin Hao
2022-09-29 8:52 ` Peter Zijlstra [this message]
2022-09-29 9:07 ` haoxin
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=YzVc6UwLSwkG7jKX@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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=namit@vmware.com \
--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