From: David Hildenbrand <david@redhat.com>
To: Peter Xu <peterx@redhat.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, linux-mm@kvack.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
Axel Rasmussen <axelrasmussen@google.com>
Subject: Re: [PATCH v3] madvise.2: Clarify addr/length and update hugetlb support
Date: Fri, 10 Jun 2022 11:01:25 +0200 [thread overview]
Message-ID: <05301a1a-6020-aa52-d539-c2e0ba147181@redhat.com> (raw)
In-Reply-To: <YqJUZcol6c7HL6Dt@xz-m1.local>
On 09.06.22 22:13, Peter Xu wrote:
> On Thu, Jun 09, 2022 at 11:48:06AM -0700, Mike Kravetz wrote:
>> On 6/9/22 06:24, Alejandro Colomar wrote:
>>> Hi Mike,
>>>
>>> On 6/9/22 01:45, Mike Kravetz wrote:
>>>> Clarify that madvise only works on full pages, and remove references
>>>> to 'bytes'.
>>>>
>>>> Update MADV_DONTNEED and MADV_REMOVE sections to remove notes that
>>>> HugeTLB mappings are not supported. Indicate the releases when they
>>>> were first supported as well as alignment restrictions.
>>>>
>>>> Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
>>>> Acked-by: Peter Xu <peterx@redhat.com>
>>>
>>> Please check some comments below.
>>>
>>> Thanks,
>>>
>>
>> Thank you!
>>
>> And, my apologies for not looking at formatting requirements.
>> Will send a v4 shortly.
>
> Alex,
>
> Do you think we could add some of the semantic newline requirement into
> CONTRIBUTING file explicitly? Although there's a pointer to man7 man-pages
> but the semantic newlines rules seem to be easily overlooked.
>
> IMHO there can even be examples as you quoted in the link on "UNIX For
> Beginners":
>
> https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/man7/man-pages.7?h=alx/main&id=6ff6f43d68164f99a8c3fb66f4525d145571310c
>
> Maybe that'll ease both the maintainers and the contributors?
Maybe something similar checkpatch in Linux/qemu could point out a lot
of these possible issues and reduce Maintainer overhead. Nobody reads
docs after all if not forced to ;)
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-06-10 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 23:45 Mike Kravetz
2022-06-09 13:24 ` Alejandro Colomar
2022-06-09 18:48 ` Mike Kravetz
2022-06-09 20:13 ` Peter Xu
2022-06-10 9:01 ` David Hildenbrand [this message]
2022-06-10 9:38 ` Alejandro Colomar
2022-06-10 14:07 ` Peter Xu
2022-06-10 14:41 ` Alejandro Colomar
2022-08-15 20:41 ` Alejandro Colomar
2022-08-15 20:46 ` Alejandro Colomar
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=05301a1a-6020-aa52-d539-c2e0ba147181@redhat.com \
--to=david@redhat.com \
--cc=alx.manpages@gmail.com \
--cc=axelrasmussen@google.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=mtk.manpages@gmail.com \
--cc=peterx@redhat.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