From: Peter Xu <peterx@redhat.com>
To: John Hubbard <jhubbard@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Mike Kravetz <mike.kravetz@oracle.com>
Subject: Re: [PATCH] mm/hugetlb: Drop __unmap_hugepage_range definition from hugetlb.h
Date: Thu, 16 Sep 2021 20:03:28 -0400 [thread overview]
Message-ID: <YUPbUEjhvPL/VArw@t490s> (raw)
In-Reply-To: <b99f88db-edeb-fab1-803e-5e083594bec8@nvidia.com>
On Thu, Sep 16, 2021 at 03:57:38PM -0700, John Hubbard wrote:
> On 9/16/21 14:28, Peter Xu wrote:
> > Drop it in the header since it's only used in hugetlb.c.
>
> Hi Peter,
Hi, John,
>
> Tiny documentation tweak: could the above line please be changed to
> something approximately like this:
>
> "Remove __unmap_hugepage_range() from the header file, because it is
> only used in the .c file."
>
> ?
Sure thing.
>
> Because: "drop it in" is so close to "drop it into" (which means, "add
> it to"), that it's actually reading a lot like the opposite of what you
> intend to say.
>
> >
> > Suggested-by: Mike Kravetz <mike.kravetz@oracle.com>
> > Signed-off-by: Peter Xu <peterx@redhat.com>
> > ---
> > include/linux/hugetlb.h | 10 ----------
> > mm/hugetlb.c | 6 +++---
> > 2 files changed, 3 insertions(+), 13 deletions(-)
>
>
> The change itself looks accurate for the current top of tree, so:
>
> Reviewed-by: John Hubbard <jhubbard@nvidia.com>
Thanks!
--
Peter Xu
next prev parent reply other threads:[~2021-09-17 0:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 21:28 [PATCH] mm/hugetlb: Drop __unmap_hugepage_range definition from hugetlb.h Peter Xu
2021-09-16 22:41 ` Mike Kravetz
2021-09-16 22:57 ` John Hubbard
2021-09-17 0:03 ` Peter Xu [this message]
2021-09-17 3:27 ` Muchun Song
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=YUPbUEjhvPL/VArw@t490s \
--to=peterx@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jhubbard@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.