From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux CGroups <cgroups@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Cc: Tejun Heo <tj@kernel.org>, Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Jonathan Corbet <corbet@lwn.net>, Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Shakeel Butt <shakeelb@google.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH v2 0/9] docs: cgroup-v1: formatting improv for "Memory Resource Controller" doc
Date: Thu, 5 Jan 2023 20:16:25 +0700 [thread overview]
Message-ID: <20230105131633.553574-1-bagasdotme@gmail.com> (raw)
"Memory Resource Controller" CGroup v1 documentation has been in reST since
99c8b231ae6c6c ("docs: cgroup-v1: convert docs to ReST and rename to *.rst").
The current doc look is kinda ugly, so improve the formatting (only htmldocs is
tested).
Changes since v1 [1]:
* Drop the underline fix, since the blamed commit had been dropped
* Rebase on top of current cgroup tree (for-next branch)
Range-diff against v1:
1: e0f2b878ad6435 < -: -------------- docs: cgroup-v1: extend underline of section 8
2: 4e26b743ce9b42 = 1: cb31249cacdad6 docs: cgroup-v1: replace custom note constructs with appropriate admonition blocks
3: c89f9aa1e6dac9 < -: -------------- docs: cgroup-v1: wrap remaining admonitions in admonition blocks
-: -------------- > 2: 8e03baf289c4f2 docs: cgroup-v1: wrap remaining admonitions in admonition blocks
4: b901b2b0407e23 = 3: 790ac70bcf31e1 docs: cgroup-v1: use code block for locking order schema
5: f4112d2f9990ce = 4: 2af22c24977a38 docs: cgroup-v1: fix footnotes
6: d5d16831555e6b = 5: 9788d0e8c87cc5 docs: cgroup-v1: move hierarchy of accounting caption
7: 92db959851e2c8 = 6: b191e2bd87871b docs: cgroup-v1: use bullet lists for list of stat file tables
8: 767988658f58b8 ! 7: 56e4ba363e4e65 docs: cgroup-v1: use make swap extension subsections subsections
@@ Metadata
Author: Bagas Sanjaya <bagasdotme@gmail.com>
## Commit message ##
- docs: cgroup-v1: use make swap extension subsections subsections
+ docs: cgroup-v1: make swap extension subsections subsections
Subsections text of swap extension section is marked up as bold text,
whereas making them proper subsection is more appropriate.
9: a502f09f9a3c33 ! 8: 6895ee7c84e840 docs: cgroup-v1: add internal cross-references
@@ Documentation/admin-guide/cgroup-v1/memory.rst: If we want to change this to 1G,
+.. _cgroup-v1-memory-move-charges:
+
- 8. Move charges at task migration (DEPRECATED!)
- ===============================================
+ 8. Move charges at task migration
+ =================================
@@ Documentation/admin-guide/cgroup-v1/memory.rst: If you want to enable it::
10: 895b1f1aa37d33 = 9: b179c2788f2a36 docs: cgroup-v1: use numbered lists for user interface setup
[1]: https://lore.kernel.org/linux-doc/20221219042209.22898-1-bagasdotme@gmail.com/
Bagas Sanjaya (9):
docs: cgroup-v1: replace custom note constructs with appropriate
admonition blocks
docs: cgroup-v1: wrap remaining admonitions in admonition blocks
docs: cgroup-v1: use code block for locking order schema
docs: cgroup-v1: fix footnotes
docs: cgroup-v1: move hierarchy of accounting caption
docs: cgroup-v1: use bullet lists for list of stat file tables
docs: cgroup-v1: make swap extension subsections subsections
docs: cgroup-v1: add internal cross-references
docs: cgroup-v1: use numbered lists for user interface setup
.../admin-guide/cgroup-v1/cgroups.rst | 2 +
.../admin-guide/cgroup-v1/memory.rst | 268 ++++++++++--------
2 files changed, 146 insertions(+), 124 deletions(-)
base-commit: 21786e5cb375a1e58a9175fee423e1d7f892d965
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-01-05 13:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 13:16 Bagas Sanjaya [this message]
2023-01-05 13:16 ` [PATCH v2 1/9] docs: cgroup-v1: replace custom note constructs with appropriate admonition blocks Bagas Sanjaya
2023-01-05 13:16 ` [PATCH v2 2/9] docs: cgroup-v1: wrap remaining admonitions in " Bagas Sanjaya
2023-01-05 13:16 ` [PATCH v2 3/9] docs: cgroup-v1: use code block for locking order schema Bagas Sanjaya
2023-01-05 13:16 ` [PATCH v2 4/9] docs: cgroup-v1: fix footnotes Bagas Sanjaya
2023-01-05 13:16 ` [PATCH v2 5/9] docs: cgroup-v1: move hierarchy of accounting caption Bagas Sanjaya
2023-01-05 13:16 ` [PATCH v2 6/9] docs: cgroup-v1: use bullet lists for list of stat file tables Bagas Sanjaya
2023-01-05 13:16 ` [PATCH v2 7/9] docs: cgroup-v1: make swap extension subsections subsections Bagas Sanjaya
2023-01-05 13:16 ` [PATCH v2 8/9] docs: cgroup-v1: add internal cross-references Bagas Sanjaya
2023-01-05 13:16 ` [PATCH v2 9/9] docs: cgroup-v1: use numbered lists for user interface setup Bagas Sanjaya
2023-01-05 17:39 ` [PATCH v2 0/9] docs: cgroup-v1: formatting improv for "Memory Resource Controller" doc Tejun Heo
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=20230105131633.553574-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan.x@bytedance.com \
--cc=mhocko@suse.com \
--cc=shakeelb@google.com \
--cc=tj@kernel.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