From: Mike Rapoport <rppt@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
David Hildenbrand <david@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Lorenzo Stoakes <lstoakes@gmail.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Mel Gorman <mgorman@suse.de>, Michal Hocko <mhocko@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v4 0/1] docs/mm: start filling out new structure
Date: Sun, 22 Jan 2023 07:30:54 +0200 [thread overview]
Message-ID: <Y8zKDkJPeEb0wUTK@kernel.org> (raw)
In-Reply-To: <20230115184212.996298-1-rppt@kernel.org>
Gentle ping.
On Sun, Jan 15, 2023 at 08:42:11PM +0200, Mike Rapoport wrote:
> Hi,
>
> Last year at LSF/MM Matthew promptly created the new structure for MM
> documentation, but there still was no patches with content.
>
> I've started to work on it a while ago and I wanted to send it out in a
> more complete form, but I've got distracted and didn't have time to work
> on this.
>
> With fast changes around struct page and the threat of Lorenzo's book,
> I've decided to send out what I have till now with a hope that we can
> really make this a collaborative effort with people filling paragraph
> here and there.
>
> If somebody does not feel like sending formal patches, just send me the
> "raw" text my way and I'll deal with the rest.
>
> The text is relatively heavily formatted because I believe the target
> audience will prefer html version.
>
> v4:
> * squash commits into one (Bagas)
> * fix references formatting (kbuild)
> * add Reviewed-by and Acked-by tags
>
> v3: https://lore.kernel.org/all/20230112091616.824565-1-rppt@kernel.org
> * rephrase ZONE_DMA(32) and ZONE_MOVABLE description (Michal)
> * add cross-reference to DMA API
>
> v2: https://lore.kernel.org/all/20230110152358.2641910-1-rppt@kernel.org
> * rephrase the paragraph inroducing zones (Lorenzo)
> * update formatting (Bagas)
> * add section stubs (Bagas)
> * small fixes here and there
>
> v1: https://lore.kernel.org/all/20230101094523.1522109-1-rppt@kernel.org
>
> Mike Rapoport (IBM) (1):
> docs/mm: Physical Memory: add structure, introduction and nodes
> description
>
> Documentation/core-api/dma-api.rst | 2 +
> Documentation/mm/page_reclaim.rst | 2 +
> Documentation/mm/physical_memory.rst | 346 +++++++++++++++++++++++++++
> 3 files changed, 350 insertions(+)
>
> --
> 2.35.1
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2023-01-22 5:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 18:42 [PATCH v4 0/1] docs/mm: start filling out new structure Mike Rapoport
2023-01-15 18:42 ` [PATCH v4 1/1] docs/mm: Physical Memory: add structure, introduction and nodes description Mike Rapoport
2023-01-24 11:00 ` Vlastimil Babka
2023-01-24 11:16 ` Mike Rapoport
2023-01-24 13:40 ` Vlastimil Babka
2023-01-25 18:56 ` Mike Rapoport
2023-01-22 5:30 ` Mike Rapoport [this message]
2023-01-22 17:43 ` [PATCH v4 0/1] docs/mm: start filling out new structure Jonathan Corbet
2023-01-22 18:41 ` 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=Y8zKDkJPeEb0wUTK@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=vbabka@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).