From: Mike Rapoport <rppt@kernel.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: SeongJae Park <sj@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
Alice Ryhl <aliceryhl@google.com>,
Boqun Feng <boqun.feng@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Suren Baghdasaryan <surenb@google.com>,
linux-doc@vger.kernel.org
Subject: Re: [RFC PATCH] docs/mm: add VMA locks documentation
Date: Mon, 4 Nov 2024 15:47:40 +0200 [thread overview]
Message-ID: <ZyjQfG2YakYXLUdS@kernel.org> (raw)
In-Reply-To: <b5fcdae7-8918-451c-ab7a-de7136e5dbe3@lucifer.local>
On Mon, Nov 04, 2024 at 01:02:19PM +0000, Lorenzo Stoakes wrote:
> On Fri, Nov 01, 2024 at 04:48:32PM -0700, SeongJae Park wrote:
> >
> > This is the "Unsorted Documentation" section. If the document is really for
> > the section, I'd suggest putting it in alphabetically sorted order, for the
> > consistency. However, if putting the document under the section is not your
> > real intention, I think it might be better to be put under "Process Addresses"
> > section above. What do you think?
>
> Well, at the moment it's sort of a WIP thing that we may want to put under
> another section, was just putting there somewhat arbitrarily for now.
>
> I also wanted to avoid too much debate about what to put where :P
>
> But absolutely, ack, will either sort it there or put it somewhere more
> sensible, thanks!
Don't mean to bikeshed, but it would make sense to put it to the "Process
Address (space)" part :)
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2024-11-04 13:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 18:50 Lorenzo Stoakes
2024-11-01 20:58 ` Lorenzo Stoakes
2024-11-01 22:41 ` Suren Baghdasaryan
2024-11-01 23:48 ` SeongJae Park
2024-11-04 13:02 ` Lorenzo Stoakes
2024-11-04 13:47 ` Mike Rapoport [this message]
2024-11-04 19:55 ` Lorenzo Stoakes
2024-11-02 1:45 ` Jann Horn
2024-11-04 16:42 ` Lorenzo Stoakes
2024-11-04 21:29 ` Jann Horn
2024-11-05 16:10 ` Lorenzo Stoakes
2024-11-05 17:21 ` Jann Horn
2024-11-06 3:09 ` Qi Zheng
2024-11-06 18:09 ` Jann Horn
2024-11-07 7:07 ` Qi Zheng
2024-11-06 2:56 ` Qi Zheng
2024-11-06 11:28 ` Lorenzo Stoakes
2024-11-07 6:47 ` Qi Zheng
2024-11-02 9:00 ` Mike Rapoport
2024-11-04 14:17 ` Lorenzo Stoakes
2024-11-04 15:19 ` Mike Rapoport
2024-11-05 12:23 ` Lorenzo Stoakes
2024-11-04 14:47 ` Alice Ryhl
2024-11-04 16:52 ` Lorenzo Stoakes
2024-11-05 13:56 ` Alice Ryhl
2024-11-05 14:18 ` Lorenzo Stoakes
2024-11-04 17:01 ` Suren Baghdasaryan
2024-11-04 21:04 ` Lorenzo Stoakes
2024-11-04 21:20 ` Suren Baghdasaryan
2024-11-05 16:11 ` Lorenzo Stoakes
2024-11-04 21:25 ` Jann Horn
2024-11-07 11:07 ` Hillf Danton
2024-11-07 11:15 ` Lorenzo Stoakes
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=ZyjQfG2YakYXLUdS@kernel.org \
--to=rppt@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=jannh@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=sj@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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