From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
akpm@linux-foundation.org, rppt@kernel.org, peterz@infradead.org,
tsbogend@alpha.franken.de, will@kernel.org, maobibo@loongson.cn,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Few spelling fixes
Date: Thu, 18 Mar 2021 11:19:56 -0700 [thread overview]
Message-ID: <302bb00b-df7b-970a-1c47-b48a56c7a526@infradead.org> (raw)
In-Reply-To: <20210318065831.9601-1-unixbhaskar@gmail.com>
On 3/17/21 11:58 PM, Bhaskar Chowdhury wrote:
>
> Few spelling fixes throughout the file.
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> include/linux/pgtable.h | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/include/linux/pgtable.h b/include/linux/pgtable.h
> index 5e772392a379..4fcefd553a5c 100644
> --- a/include/linux/pgtable.h
> +++ b/include/linux/pgtable.h
> @@ -852,7 +852,7 @@ static inline void __ptep_modify_prot_commit(struct vm_area_struct *vma,
> * updates, but to prevent any updates it may make from being lost.
> *
> * This does not protect against other software modifications of the
> - * pte; the appropriate pte lock must be held over the transation.
> + * pte; the appropriate pte lock must be held over the transition.
I think that should be transaction.
> *
> * Note that this interface is intended to be batchable, meaning that
> * ptep_modify_prot_commit may not actually update the pte, but merely
Other changes are OK.
--
~Randy
prev parent reply other threads:[~2021-03-18 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 6:58 [PATCH] mm: Few spelling fixes Bhaskar Chowdhury
2021-03-18 18:19 ` Randy Dunlap [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=302bb00b-df7b-970a-1c47-b48a56c7a526@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maobibo@loongson.cn \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=unixbhaskar@gmail.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).