From: David Hildenbrand <david@redhat.com>
To: Zhiyuan Dai <daizhiyuan@phytium.com.cn>,
mike.kravetz@oracle.com, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/hugetlb.c: Fix typos in comments
Date: Tue, 2 Feb 2021 10:42:22 +0100 [thread overview]
Message-ID: <4027b34b-4407-91cd-2b9c-3065044a31d0@redhat.com> (raw)
In-Reply-To: <1612255593-8451-1-git-send-email-daizhiyuan@phytium.com.cn>
On 02.02.21 09:46, Zhiyuan Dai wrote:
> Signed-off-by: Zhiyuan Dai <daizhiyuan@phytium.com.cn>
> ---
> mm/hugetlb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index 18f6ee3..35db386 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -3990,7 +3990,7 @@ void unmap_hugepage_range(struct vm_area_struct *vma, unsigned long start,
>
> /*
> * This is called when the original mapper is failing to COW a MAP_PRIVATE
> - * mappping it owns the reserve page for. The intention is to unmap the page
> + * mapping it owns the reserve page for. The intention is to unmap the page
> * from other VMAs and let the children be SIGKILLed if they are faulting the
> * same region.
> */
>
I'm really sorry, but sending four times the same patch with different
things messed up just for fixing a simple typo is absolutely annoying.
Please exercise sending patches somewhere else. This is just unnecessary
noise on linux-mm.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-02-02 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 8:46 [PATCH] mm/hugetlb.c: Fix typos in comments Zhiyuan Dai
2021-02-02 9:42 ` David Hildenbrand [this message]
2021-02-02 8:55 Zhiyuan Dai
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=4027b34b-4407-91cd-2b9c-3065044a31d0@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=daizhiyuan@phytium.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.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;
as well as URLs for NNTP newsgroup(s).