From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jingyu Wang <jingyuwang_vip@163.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/gup.c: fix typo in comments
Date: Sat, 25 Mar 2023 20:06:58 +0700 [thread overview]
Message-ID: <ZB7x8mr8Lf27PP6Q@debian.me> (raw)
In-Reply-To: <20230309104813.170309-1-jingyuwang_vip@163.com>
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
On Thu, Mar 09, 2023 at 06:48:13PM +0800, Jingyu Wang wrote:
> Signed-off-by: Jingyu Wang <jingyuwang_vip@163.com>
What? No description, really? And Fixes: what?
> - * and subsequently re faulted). However it does guarantee that the page
> + * and subsequently re-faulted). However it does guarantee that the page
Or refaulted?
I'm kinda confused...
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
parent reply other threads:[~2023-03-25 13:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230309104813.170309-1-jingyuwang_vip@163.com>]
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=ZB7x8mr8Lf27PP6Q@debian.me \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jingyuwang_vip@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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