From: Vlastimil Babka <vbabka@suse.cz>
To: Yixuan Cao <caoyixuan2019@email.szu.edu.cn>, akpm@linux-foundation.org
Cc: cl@linux.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, roman.gushchin@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/slab.c: fix comments
Date: Thu, 7 Apr 2022 11:46:51 +0200 [thread overview]
Message-ID: <b2bd760f-b4aa-d357-e3a9-4236228225f9@suse.cz> (raw)
In-Reply-To: <20220407080958.3667-1-caoyixuan2019@email.szu.edu.cn>
On 4/7/22 10:09, Yixuan Cao wrote:
> While reading the source code,
> I noticed some language errors in the comments, so I fixed them.
>
> Signed-off-by: Yixuan Cao <caoyixuan2019@email.szu.edu.cn>
Added to slab tree, thanks.
prev parent reply other threads:[~2022-04-07 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 8:09 Yixuan Cao
2022-04-07 8:53 ` Hyeonggon Yoo
2022-04-07 9:46 ` Vlastimil Babka [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=b2bd760f-b4aa-d357-e3a9-4236228225f9@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=caoyixuan2019@email.szu.edu.cn \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
/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