From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Mike Rapoport <rppt@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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 v3 0/3] docs/mm: start filling out new structure
Date: Fri, 13 Jan 2023 15:38:47 +0700 [thread overview]
Message-ID: <Y8EYl5FNaA3Wa3So@debian.me> (raw)
In-Reply-To: <20230112091616.824565-1-rppt@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
On Thu, Jan 12, 2023 at 11:16:13AM +0200, Mike Rapoport wrote:
> Mike Rapoport (IBM) (3):
> docs/core-api: DMA API: add page label to allow external references
> docs/mm: Page Reclaim: add page label to allow external references
> docs/mm: Physical Memory: add structure, introduction and nodes
> description
I'd like to squash [1/3] and [2/3] to actual doc [3/3], for which the
latter contains cross-references to labels defined in the former.
Indeed, IMO, adding required reference labels in some other place when
writing the doc can be constituted as part of writing the doc itself.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-01-13 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 9:16 Mike Rapoport
2023-01-12 9:16 ` [PATCH v3 1/3] docs/core-api: DMA API: add page label to allow external references Mike Rapoport
2023-01-12 9:16 ` [PATCH v3 2/3] docs/mm: Page Reclaim: " Mike Rapoport
2023-01-12 9:16 ` [PATCH v3 3/3] docs/mm: Physical Memory: add structure, introduction and nodes description Mike Rapoport
2023-01-13 8:34 ` Bagas Sanjaya
2023-01-13 13:09 ` Michal Hocko
2023-01-13 13:35 ` Lorenzo Stoakes
2023-01-13 8:38 ` Bagas Sanjaya [this message]
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=Y8EYl5FNaA3Wa3So@debian.me \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--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=rppt@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