From: Ira Weiny <ira.weiny@intel.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [LSF/MM/BPF TOPIC]: MM documentation
Date: Sun, 16 Feb 2020 17:10:10 -0800 [thread overview]
Message-ID: <20200217011009.GA4660@iweiny-DESK2.sc.intel.com> (raw)
In-Reply-To: <20200206165305.GB17499@linux.ibm.com>
On Thu, Feb 06, 2020 at 06:53:05PM +0200, Mike Rapoport wrote:
> The mm documentation is, well, not entirely up to date. We can opt for
> dropping the outdated parts, which would generate a nice negative
> diffstat, but identifying the outdated documentation requires nearly
> as much effort as updating it, so I think that making and keeping
> the docs up to date would be a better option.
>
> I'd like to discuss what can be done process-wise to improve the
> situation.
>
> Some points I had in mind:
>
> * Pay more attention to docs during review
> * Set an expectation level for docs accompanying a changeset
> * Spend some cycles to review and update the existing docs
> * Spend some more cycles to add new documentation
As a newcomer to the MM area of the kernel I would like to see more of this as
well.
Ira
>
> I'd appreciate a discussion about how we can get to the second edition
> of "Understanding the Linux Virtual Memory Manager", what are the gaps
> (although they are too many), and what would be the best way to close
> these gaps.
>
> --
> Sincerely yours,
> Mike.
>
>
next prev parent reply other threads:[~2020-02-17 1:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 16:53 Mike Rapoport
2020-02-17 1:10 ` Ira Weiny [this message]
2020-02-22 2:15 ` John Hubbard
2022-02-01 19:03 [LSF/MM/BPF TOPIC] mm documentation Mike Rapoport
2023-05-12 1:39 ` Lorenzo Stoakes
2023-05-12 17:37 ` Mike Rapoport
2023-05-13 11:21 ` Lorenzo Stoakes
2023-05-15 6:07 ` Mike Rapoport
2023-05-16 15:10 ` Jonathan Corbet
2023-05-21 23:50 ` David Rientjes
2023-05-22 7:47 ` Lorenzo Stoakes
2023-05-23 8:50 ` Mike Rapoport
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=20200217011009.GA4660@iweiny-DESK2.sc.intel.com \
--to=ira.weiny@intel.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=rppt@linux.ibm.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