All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Suren Baghdasaryan <surenb@google.com>,
	"Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	Jann Horn <jannh@google.com>,
	Qi Zheng <zhengqi.arch@bytedance.com>,
	linux-mm@kvack.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/mm: expand vma doc to highlight pte freeing, non-vma traversal
Date: Tue, 03 Jun 2025 08:37:23 -0600	[thread overview]
Message-ID: <87tt4w7uxo.fsf@trenco.lwn.net> (raw)
In-Reply-To: <ea8c2be9-0af0-445b-b7fe-fd9e80bd6a65@lucifer.local>

Lorenzo Stoakes <lorenzo.stoakes@oracle.com> writes:

> But to repeat - 'given C's weirdness with typing I really prefer to be
> explicit in referencing a struct vs. e.g. a typedef.'

...and I think that makes perfect sense.

>> Why would you *not* want to cross-reference something and make life easier
>> for your reader?
>
> Because it apparently requires me to document every function I reference?
> Unless I'm missing something?
>
> I may be misunderstanding you.
>
> If not then fine, I can delay this patch, go off and do a 'cleanup' patch
> first, that will drop the '!'s and come back to this.
>
> But if I need to document every referenced function that just isn't
> feasible for me with my current workload.
>
> Please clarify!

Hopefully I already have - I'm in no position to enforce such a
requirement, even if I thought it would be a good thing -- and I don't.
It's hard enough to get documentation written as it is, I certainly
don't want to make it harder.

My suggestion would be: proceed with your changes for now, it was never
my purpose to put obstacles there.  I'll look at having automarkup do
something a bit more useful for references that lack documentation, then
maybe I'll do a cleanup pass on some of the mm docs if nobody else gets
there first.

Thanks,

jon

  reply	other threads:[~2025-06-03 14:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02 21:07 [PATCH] docs/mm: expand vma doc to highlight pte freeing, non-vma traversal Lorenzo Stoakes
2025-06-02 21:38 ` Jonathan Corbet
2025-06-03 10:56   ` Lorenzo Stoakes
2025-06-03 11:24     ` Lorenzo Stoakes
2025-06-03 14:01       ` Jonathan Corbet
2025-06-03 14:11         ` Lorenzo Stoakes
2025-06-03 14:33           ` Jonathan Corbet
2025-06-03 14:08     ` Jonathan Corbet
2025-06-03 14:24       ` Lorenzo Stoakes
2025-06-03 14:37         ` Jonathan Corbet [this message]
2025-06-03 14:52           ` Lorenzo Stoakes
2025-06-03 15:05             ` Jonathan Corbet
2025-06-03 15:14               ` Lorenzo Stoakes
2025-06-03 15:28                 ` Jonathan Corbet
2025-06-02 22:25 ` Jann Horn
2025-06-03 10:45   ` Lorenzo Stoakes
2025-06-03 18:36     ` Jann Horn
2025-06-03 18:52       ` 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=87tt4w7uxo.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --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=shakeel.butt@linux.dev \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=zhengqi.arch@bytedance.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.