From: Wei Yang <richard.weiyang@gmail.com>
To: Jianyun Gao <jianyungao89@gmail.com>
Cc: dev.jain@arm.com, Liam.Howlett@oracle.com,
akpm@linux-foundation.org, baohua@kernel.org, bhe@redhat.com,
chengming.zhou@linux.dev, chrisl@kernel.org, cl@gentwo.org,
damon@lists.linux.dev, david@redhat.com, dvyukov@google.com,
elver@google.com, glider@google.com, harry.yoo@oracle.com,
jannh@google.com, jgg@ziepe.ca, jhubbard@nvidia.com,
kasan-dev@googlegroups.com, kasong@tencent.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lorenzo.stoakes@oracle.com, mhocko@suse.com, nphamcs@gmail.com,
peterx@redhat.com, pfalcato@suse.de, rientjes@google.com,
roman.gushchin@linux.dev, rppt@kernel.org,
shikemeng@huaweicloud.com, sj@kernel.org, surenb@google.com,
vbabka@suse.cz, xu.xin16@zte.com.cn
Subject: Re: [PATCH v2] mm: Fix some typos in mm module
Date: Mon, 29 Sep 2025 11:43:02 +0000 [thread overview]
Message-ID: <20250929114302.eshtdbqkjiuflsib@master> (raw)
In-Reply-To: <20250929002608.1633825-1-jianyungao89@gmail.com>
On Mon, Sep 29, 2025 at 08:26:08AM +0800, Jianyun Gao wrote:
>From: "jianyun.gao" <jianyungao89@gmail.com>
>
>Below are some typos in the code comments:
>
> intevals ==> intervals
> addesses ==> addresses
> unavaliable ==> unavailable
> facor ==> factor
> droping ==> dropping
> exlusive ==> exclusive
> decription ==> description
> confict ==> conflict
> desriptions ==> descriptions
> otherwize ==> otherwise
> vlaue ==> value
> cheching ==> checking
> exisitng ==> existing
> modifed ==> modified
> differenciate ==> differentiate
> refernece ==> reference
> permissons ==> permissions
> indepdenent ==> independent
> spliting ==> splitting
>
>Just fix it.
>
>Signed-off-by: jianyun.gao <jianyungao89@gmail.com>
LGTM
Reviewed-by: Wei Yang <richard.weiyang@gmail.com>
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2025-09-29 11:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-27 8:06 [PATCH] " jianyun.gao
2025-09-27 17:20 ` SeongJae Park
2025-09-28 1:29 ` Wei Yang
2025-09-28 12:53 ` Dev Jain
2025-09-29 0:26 ` [PATCH v2] " Jianyun Gao
2025-09-29 3:36 ` Dev Jain
2025-09-29 11:43 ` Wei Yang [this message]
2025-09-29 14:42 ` [PATCH] " Liam R. Howlett
2025-09-29 18:17 ` Chris Li
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=20250929114302.eshtdbqkjiuflsib@master \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=bhe@redhat.com \
--cc=chengming.zhou@linux.dev \
--cc=chrisl@kernel.org \
--cc=cl@gentwo.org \
--cc=damon@lists.linux.dev \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=harry.yoo@oracle.com \
--cc=jannh@google.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=jianyungao89@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=nphamcs@gmail.com \
--cc=peterx@redhat.com \
--cc=pfalcato@suse.de \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=rppt@kernel.org \
--cc=shikemeng@huaweicloud.com \
--cc=sj@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=xu.xin16@zte.com.cn \
/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