From: Hugh Dickins <hughd@google.com>
To: Kit Dallege <xaum.io@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
david@kernel.org, linux-mm@kvack.org, linux-doc@vger.kernel.org,
Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [PATCH] Docs/mm: document Shared Memory Filesystem
Date: Sat, 14 Mar 2026 14:01:07 -0700 (PDT) [thread overview]
Message-ID: <b4203018-78a1-2e24-fa65-b02553abcea3@google.com> (raw)
In-Reply-To: <CAAZVx9_6ecePCB1MMRa0q8V4afa=zRSmcaiozaFPDrrK-+bv5w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
On Sat, 14 Mar 2026, Kit Dallege wrote:
> Hi Andrew,
>
> Thanks for the positive feedback. I'll add the Assisted-by tag in v2.
>
> To clarify — I used Gorman's book as a reference for understanding the
> subsystem structure, not as a source to copy from. The documentation was
> written by reading the current source code and verified against it. I
> didn't contact Mel beforehand but the book outline was only used to
> identify which topics each stub file should cover.
>
> Happy to have the relevant MM developers review each patch. Should I
> resend the series with the Assisted-by tags, or wait for further
> feedback first?
>
> Thanks,
> Kit
And now the negative feedback: thanks, but NAK to this particular patch.
Documentation/mm/shmfs.rst? I hadn't realized that such a file existed.
tmpfs has been known as tmpfs since 2.4.4 (but a few people do still say
shmfs, and I'd agree with them that shmfs would have been a better name).
Please send a patch, either to delete shmfs.rst and its index entry,
or to redirect its readers to
Documentation/filesystems/tmpfs.rst
I haven't looked up the preferred way to redirect in Documentation:
I expect Jon or Claude can assist you with that :-)
Hugh
next prev parent reply other threads:[~2026-03-14 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 15:25 [PATCH] Docs/mm: document Shared Memory Filesystem Kit Dallege
2026-03-14 15:46 ` Jonathan Corbet
2026-03-14 16:02 ` Kit Dallege
2026-03-14 18:17 ` Andrew Morton
2026-03-14 18:38 ` Kit Dallege
2026-03-14 21:01 ` Hugh Dickins [this message]
2026-03-15 19:50 ` David Hildenbrand (arm)
2026-03-15 19:55 ` David Hildenbrand (arm)
2026-03-15 19:59 ` Mike Rapoport
2026-03-15 20:03 ` Mike Rapoport
2026-03-15 20:00 ` Lorenzo Stoakes (Oracle)
2026-03-15 20:14 ` Lorenzo Stoakes (Oracle)
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=b4203018-78a1-2e24-fa65-b02553abcea3@google.com \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=xaum.io@gmail.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