From: Randy Dunlap <rdunlap@infradead.org>
To: Suren Baghdasaryan <surenb@google.com>, SeongJae Park <sj@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Kent Overstreet <kent.overstreet@linux.dev>
Subject: Re: [PATCH 4/4] Docs/mm/index: move allocation profiling document to unsorted documents chapter
Date: Wed, 3 Jul 2024 19:18:32 -0700 [thread overview]
Message-ID: <1d805df8-748a-4bbc-a3d9-d6aa01a0b16e@infradead.org> (raw)
In-Reply-To: <CAJuCfpFO_C_LgxrRWrxG9o==RRtYAbkbP3ZJULwdmTjDcAJNrg@mail.gmail.com>
On 7/3/24 7:10 PM, Suren Baghdasaryan wrote:
> On Wed, Jul 3, 2024 at 4:00 PM SeongJae Park <sj@kernel.org> wrote:
>>
>> On Wed, 03 Jul 2024 16:18:42 -0600 Jonathan Corbet <corbet@lwn.net> wrote:
>>
>>> SeongJae Park <sj@kernel.org> writes:
>>>
>>>> The memory allocation profiling document was added to the bottom of the
>>>> new outline. Apparently it was not decided by well-defined guidelines
>>>> or a thorough discussions. Rather than that, it was added there just
>>>> because there was no place for such unsorted documents. Now there is
>>>> the chapter. Move the document to the new place.
>>>
>>> I'll take this for now, but it's truly sad to see new documentation
>>> being added to the slushpile at the end. It seems better to create a
>>> "development tools" section in the new outline and put the allocation
>>> profiling document there?
>>
>> I have no strong opinions about that. Cc-ing Suren and Kent, as they are the
>> author of the allocation profiling document and hence might have some opinion.
>
> IMHO if this would be the only document belonging to "development
> tools" then keeping it under unsorted is fine.
> If more documents will fall into that category then Jonathan's
> suggestion makes sense to me. Looking at the current list, page_owner
> and maybe damon might be considered for this category as well.
> SeongJae, WDYT?
> Thanks,
> Suren.
>
Documentation/dev-tools/ already contains 20 files.
Unless you want to keep it under Documentation/mm/, that is.
--
~Randy
next prev parent reply other threads:[~2024-07-04 2:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 19:05 [PATCH 0/4] Docs/mm: rename legacy docs to unsorted docs SeongJae Park
2024-07-01 19:05 ` [PATCH 1/4] Docs/mm/allocation-profiling: mark 'Theory of operation' as chapter SeongJae Park
2024-07-01 21:29 ` Suren Baghdasaryan
2024-07-01 19:05 ` [PATCH 2/4] Docs/mm/index: Remove 'Memory Management Guide' chapter marker SeongJae Park
2024-07-01 19:05 ` [PATCH 3/4] Docs/mm/index: rename 'Legacy Documentation' to 'Unsorted Documentation' SeongJae Park
2024-07-01 19:05 ` [PATCH 4/4] Docs/mm/index: move allocation profiling document to unsorted documents chapter SeongJae Park
2024-07-03 22:18 ` Jonathan Corbet
2024-07-03 23:00 ` SeongJae Park
[not found] ` <CAJuCfpFO_C_LgxrRWrxG9o==RRtYAbkbP3ZJULwdmTjDcAJNrg@mail.gmail.com>
2024-07-04 2:18 ` Randy Dunlap [this message]
2024-07-04 2:36 ` Suren Baghdasaryan
2024-07-04 3:33 ` SeongJae Park
2024-07-03 22:20 ` [PATCH 0/4] Docs/mm: rename legacy docs to unsorted docs Jonathan Corbet
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=1d805df8-748a-4bbc-a3d9-d6aa01a0b16e@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=kent.overstreet@linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sj@kernel.org \
--cc=surenb@google.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).