From: Mike Rapoport <rppt@kernel.org>
To: Lorenzo Stoakes <lstoakes@gmail.com>
Cc: linux-mm@kvack.org, Matthew Wilcox <willy@infradead.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [LSF/MM/BPF TOPIC] mm documentation
Date: Mon, 15 May 2023 09:07:43 +0300 [thread overview]
Message-ID: <ZGHMLzP2tkn2/NPh@kernel.org> (raw)
In-Reply-To: <5aa1cb82-b39e-47c9-bb7a-c6145b2acbd3@lucifer.local>
On Sat, May 13, 2023 at 12:21:18PM +0100, Lorenzo Stoakes wrote:
> On Fri, May 12, 2023 at 10:37:32AM -0700, Mike Rapoport wrote:
>
> > And if we are going to participate in projects like Outreachy and Google
> > Season of Docs, we can suggest a project "Convert Lorenzo's book to kernel
> > documentation" alongside "Write more MM documentation" project.
>
> Yeah, this could be a good starting point actually, as rather than starting
> from zero, people would have some material that they can cross-check.
I'm going to suggest "MM docs" for the next Outreachy round and I'll ping
you then about the "Convert Lorenzo's book to kernel documentation"
project.
As for participation in the Google Season of Docs, maybe this should be
more broad than only mm docs.
Jon, what do you think?
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2023-05-15 6:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 19:03 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2020-02-06 16:53 [LSF/MM/BPF TOPIC]: MM documentation Mike Rapoport
2020-02-17 1:10 ` Ira Weiny
2020-02-22 2:15 ` John Hubbard
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=ZGHMLzP2tkn2/NPh@kernel.org \
--to=rppt@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--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