From: Tejun Heo <tj@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>,
Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Shakeel Butt <shakeelb@google.com>
Subject: Re: [PATCH 00/10] docs: cgroup-v1: formatting improv for "Memory Resource Controller" doc
Date: Wed, 4 Jan 2023 06:53:59 -1000 [thread overview]
Message-ID: <Y7WvJzquc8r81X9u@slm.duckdns.org> (raw)
In-Reply-To: <87a630h5mv.fsf@meer.lwn.net>
On Mon, Jan 02, 2023 at 04:35:20PM -0700, Jonathan Corbet wrote:
> Bagas Sanjaya <bagasdotme@gmail.com> writes:
>
> > "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).
> >
> > The first patch is a fix for recently reported htmldocs warning, which can
> > be pickup separately from rest of the series.
> >
> > Bagas Sanjaya (10):
> > docs: cgroup-v1: extend underline of section 8
> > 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: use 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 | 290 ++++++++++--------
> > 2 files changed, 158 insertions(+), 134 deletions(-)
>
> Tejun, do you have an opinion on these? I'm not really sure we need to
> be tweaking the v1 docs at this point, but I don't see anything in here
> that seems harmful either...
One of the patches doesn't apply because it's against -next (it's
referencing -next sha1 too) and the series feels a bit overly elaborate but,
I mean, why not? I was planning to pick up the series after the holidays
unless you wanna route it through the doc tree.
Thanks.
--
tejun
next prev parent reply other threads:[~2023-01-04 16:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 4:21 Bagas Sanjaya
2022-12-19 4:22 ` [PATCH 01/10] docs: cgroup-v1: extend underline of section 8 Bagas Sanjaya
2022-12-19 4:22 ` [PATCH 02/10] docs: cgroup-v1: replace custom note constructs with appropriate admonition blocks Bagas Sanjaya
2022-12-19 4:22 ` [PATCH 03/10] docs: cgroup-v1: wrap remaining admonitions in " Bagas Sanjaya
2022-12-19 4:22 ` [PATCH 04/10] docs: cgroup-v1: use code block for locking order schema Bagas Sanjaya
2022-12-19 4:22 ` [PATCH 05/10] docs: cgroup-v1: fix footnotes Bagas Sanjaya
2022-12-19 4:22 ` [PATCH 06/10] docs: cgroup-v1: move hierarchy of accounting caption Bagas Sanjaya
2022-12-19 4:22 ` [PATCH 07/10] docs: cgroup-v1: use bullet lists for list of stat file tables Bagas Sanjaya
2022-12-19 4:22 ` [PATCH 08/10] docs: cgroup-v1: use make swap extension subsections subsections Bagas Sanjaya
2022-12-19 4:22 ` [PATCH 09/10] docs: cgroup-v1: add internal cross-references Bagas Sanjaya
2022-12-19 4:22 ` [PATCH 10/10] docs: cgroup-v1: use numbered lists for user interface setup Bagas Sanjaya
2023-01-02 23:35 ` [PATCH 00/10] docs: cgroup-v1: formatting improv for "Memory Resource Controller" doc Jonathan Corbet
2023-01-04 16:53 ` Tejun Heo [this message]
2023-01-04 21:27 ` Tejun Heo
2023-01-05 9:58 ` Bagas Sanjaya
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=Y7WvJzquc8r81X9u@slm.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--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 \
/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